Re: Orphaned relations after crash/sigkill during CREATE TABLE

Поиск
Список
Период
Сортировка
От Adrian Klaver
Тема Re: Orphaned relations after crash/sigkill during CREATE TABLE
Дата
Msg-id 0427412f-6d68-a1f2-72f5-14da38421769@aklaver.com
обсуждение исходный текст
Ответ на Re: Orphaned relations after crash/sigkill during CREATE TABLE  (Jason Myers <j.myers@brstrat.com>)
Список pgsql-general
On 8/18/20 1:19 PM, Jason Myers wrote:
>  > On Tue, Aug 18, 2020 at 3:49 PM Adrian Klaver 
> <adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>> wrote:
> 
>  > Have you tried with:
>  > BEGIN;
>  > CREATE TABLE some_table SELECT some_data FROM other_table LIMIT 1 WITH
>  > NO DATA;
>  > COMMIT;
>  >
>  > The above gets you the table structure, but no data.
>  >
>  > BEGIN;
>  > INSERT into some_table SELECT * FROM other_table;
>  >COMMIT;
>  >
>  > The above populates the table
> 
> Thanks -- we were indeed creating and populating the new table all in a 
> single transaction.
> 
> I'll see if we can split this into two transactions so that the table 
> structure is committed quickly.  I think you're right that this would 
> mostly sidestep the issue.

Assuming the table you are pulling from is fairly static, it could also 
allow you to regulate the amount of data you transfer at any one time 
into the new table.

> 
> -Jason
> 
> p.s. Apologies if this is formatted wrong, this is my first mailing list 
> post.


-- 
Adrian Klaver
adrian.klaver@aklaver.com



В списке pgsql-general по дате отправления:

Предыдущее
От: Matthias van de Meent
Дата:
Сообщение: Re: Index tuple deduplication limitations in pg13
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Re: Index tuple deduplication limitations in pg13