Re: continuous copy/update one table to another - Mailing list pgsql-general

From John R Pierce
Subject Re: continuous copy/update one table to another
Date
Msg-id 4B8B1463.1020209@hogranch.com
Whole thread Raw
In response to Re: continuous copy/update one table to another  (Terry <td3201@gmail.com>)
Responses Re: continuous copy/update one table to another  (Terry <td3201@gmail.com>)
List 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.









pgsql-general by date:

Previous
From: Terry
Date:
Subject: Re: continuous copy/update one table to another
Next
From: "C. Bensend"
Date:
Subject: Confusion about users and roles