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: 2010-03-01 01:12:03
Message-ID: 4B8B1463.1020209@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2010-03-01 01:48:56 Re: Confusion about users and roles
Previous Message Terry 2010-03-01 01:07:50 Re: continuous copy/update one table to another