Re: continuous copy/update one table to another

Поиск
Список
Период
Сортировка
Искать
От
John R Pierce
Тема
Re: continuous copy/update one table to another
Дата
Msg-id
4B8B1463.1020209@hogranch.com
Ответ на
Список
Дерево обсуждения
continuous copy/update one table to another Terry <td3201@gmail.com>
Re: continuous copy/update one table to another David W Noon <dwnoon@ntlworld.com>
Re: continuous copy/update one table to another Adrian von Bidder <avbidder@fortytwo.ch>
Re: continuous copy/update one table to another John R Pierce <pierce@hogranch.com>
Re: continuous copy/update one table to another Szymon Guz <mabewlun@gmail.com>
Re: continuous copy/update one table to another John R Pierce <pierce@hogranch.com>
Re: continuous copy/update one table to another Terry <td3201@gmail.com>
Re: continuous copy/update one table to another Terry <td3201@gmail.com>
Re: continuous copy/update one table to another John R Pierce <pierce@hogranch.com>
Re: continuous copy/update one table to another Terry <td3201@gmail.com>
Re: continuous copy/update one table to another Terry <td3201@gmail.com>
Re: continuous copy/update one table to another Grzegorz Jaśkiewicz <gryzman@gmail.com>
Re: continuous copy/update one table to another Szymon Guz <mabewlun@gmail.com>
Re: continuous copy/update one table to another Tom Lane <tgl@sss.pgh.pa.us>
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 по дате отправления
От: Terry
Дата:
От: C. Bensend
Дата:
FAQ