Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: continuous copy/update one table to another


  • From: John R Pierce <pierce(at)hogranch(dot)com>
  • To: pgsql-general(at)postgresql(dot)org
  • Subject: Re: continuous copy/update one table to another
  • Date: Sun, 28 Feb 2010 16:29:34 -0800
  • Message-id: <4B8B0A6E.5050703@hogranch.com> <text/plain>

Szymon Guz wrote:
Different doesn't mean that the id should be greater or lower, rather should be different. I'd rather do something like:

indeed, my code assumed that records were only INSERT'd into table1 and never UPDATE or DELETE'd. my statement -did- have the advantage of being fast, at least assuming the id is an index on both tables. if you do update records, you could use a seperate SERIAL/BIGSERIAL field for this, which you update on your INSERT's, and use this bigserial for your inserts, but you'd need a UPSERT kind of function to handle duplicate primary keys.

checking for deletions will be more difficult and more importantly, more time consuming as it will likely require multiple full table scans of both tables.





Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group