pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedInsert statement deletes older table records
4+ messages / 4 participants
[nested] [flat]
* Insert statement deletes older table records
@ 2011-05-30 00:07 Rabi Jay <rabijay1@yahoo.com>
0 siblings, 3 replies; 4+ messages in thread
From: Rabi Jay @ 2011-05-30 00:07 UTC (permalink / raw)
To: pgsql-admin
Hi,
When I execute an insert statement, older table records are deleted even though my insert statement works. It always keeps the maximum number of records in the table to 4200 records. So If I added 3 more records, it deletes the first three records in the table even though it adds the 3 new records.
Based on my research it appears postgreql has no limit to number of records in a table - what should I do to avoid this behavior.
Thanks.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Insert statement deletes older table records
@ 2011-05-30 04:21 Scott Marlowe <scott.marlowe@gmail.com>
parent: Rabi Jay <rabijay1@yahoo.com>
2 siblings, 0 replies; 4+ messages in thread
From: Scott Marlowe @ 2011-05-30 04:21 UTC (permalink / raw)
To: Rabi Jay <rabijay1@yahoo.com>; +Cc: pgsql-admin
On Sun, May 29, 2011 at 6:07 PM, Rabi Jay <rabijay1@yahoo.com> wrote:
> Hi,
>
> When I execute an insert statement, older table records are deleted even
> though my insert statement works. It always keeps the maximum number of
> records in the table to 4200 records. So If I added 3 more records, it
> deletes the first three records in the table even though it adds the 3 new
> records.
>
> Based on my research it appears postgreql has no limit to number of records
> in a table - what should I do to avoid this behavior.
This is not normal behaviour. Can you post a self-contained example
of this behaviour?
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Insert statement deletes older table records
@ 2011-05-30 10:25 Cédric Villemain <cedric.villemain.debian@gmail.com>
parent: Rabi Jay <rabijay1@yahoo.com>
2 siblings, 0 replies; 4+ messages in thread
From: Cédric Villemain @ 2011-05-30 10:25 UTC (permalink / raw)
To: Rabi Jay <rabijay1@yahoo.com>; +Cc: pgsql-admin
2011/5/30 Rabi Jay <rabijay1@yahoo.com>:
> Hi,
>
> When I execute an insert statement, older table records are deleted even
> though my insert statement works. It always keeps the maximum number of
> records in the table to 4200 records. So If I added 3 more records, it
> deletes the first three records in the table even though it adds the 3 new
> records.
>
> Based on my research it appears postgreql has no limit to number of records
> in a table - what should I do to avoid this behavior.
I think your can look at the PostgreSQL 9.1 (still in beta).
Cf doc for writable CTE :
http://www.postgresql.org/docs/9.1/static/queries-with.html
7.8.2. Data-Modifying Statements in WITH
And delete/insert in the same query.
Else there is no special feature to limit the number of rows in a table
>
> Thanks.
--
Cédric Villemain 2ndQuadrant
http://2ndQuadrant.fr/ PostgreSQL : Expertise, Formation et Support
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Insert statement deletes older table records
@ 2011-05-31 09:05 Simon Riggs <simon@2ndQuadrant.com>
parent: Rabi Jay <rabijay1@yahoo.com>
2 siblings, 0 replies; 4+ messages in thread
From: Simon Riggs @ 2011-05-31 09:05 UTC (permalink / raw)
To: Rabi Jay <rabijay1@yahoo.com>; +Cc: pgsql-admin
On Mon, May 30, 2011 at 1:07 AM, Rabi Jay <rabijay1@yahoo.com> wrote:
> When I execute an insert statement, older table records are deleted even
> though my insert statement works. It always keeps the maximum number of
> records in the table to 4200 records. So If I added 3 more records, it
> deletes the first three records in the table even though it adds the 3 new
> records.
>
> Based on my research it appears postgreql has no limit to number of records
> in a table - what should I do to avoid this behavior.
If this is a real report, please come back with further details of the
actions you are performing, version numbers and related details. If
what you say is correct then this is a data loss bug and this project
takes such things very seriously.
Having said that, this is the second time in last few months that some
"hearsay" has emerged relating to there being a limit on the number of
rows in a PostgreSQL database. So I'm a little skeptical as to this as
a credible bug report.
PostgreSQL has never had a bug filed of this nature. The described
behaviour would certainly have been picked up in testing or production
usage if it was a bug, especially since tables with 1 billion+ rows in
are fairly common.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2011-05-31 09:05 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2011-05-30 00:07 Insert statement deletes older table records Rabi Jay <rabijay1@yahoo.com>
2011-05-30 04:21 ` Scott Marlowe <scott.marlowe@gmail.com>
2011-05-30 10:25 ` Cédric Villemain <cedric.villemain.debian@gmail.com>
2011-05-31 09:05 ` Simon Riggs <simon@2ndQuadrant.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox