Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: continuous copy/update one table to another
- From: John R Pierce <pierce(at)hogranch(dot)com>
- To: Terry <td3201(at)gmail(dot)com>
- Cc: pgsql-general(at)postgresql(dot)org
- Subject: Re: continuous copy/update one table to another
- Date: Sun, 28 Feb 2010 17:12:03 -0800
- Message-id: <4B8B1463.1020209@hogranch.com> <text/plain>
Terry wrote:
One more question. This is a pretty decent sized table. It is estimated to be 19,038,200 rows. That said, should I see results immediately pouring into the destination table while this is running?
SQL transactions are atomic. you wont' see anything in the 'new' table until the INSERT finishes committing, then you'll see it all at once.
you will see a fair amount of disk write activity while its running. 20M rows will take a while to run the first time, and probably a fair amount of memory.
- References:
- continuous copy/update one table to another
- From: Terry
- Re: continuous copy/update one table to another
- From: John R Pierce
- Re: continuous copy/update one table to another
- From: Szymon Guz
- Re: continuous copy/update one table to another
- From: John R Pierce
- Re: continuous copy/update one table to another
- From: Terry
- continuous copy/update one table to another
- Prev by Date: Re: continuous copy/update one table to another
- Next by Date: Confusion about users and roles
- Previous by thread: Re: continuous copy/update one table to another
- Next by thread: Re: continuous copy/update one table to another
- Indexes: