Search Postgresql Archives

Re: Orphaned relations after crash/sigkill during CREATE TABLE

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 8/18/20 1:19 PM, Jason Myers wrote:
> On Tue, Aug 18, 2020 at 3:49 PM Adrian Klaver <adrian.klaver@xxxxxxxxxxx <mailto:adrian.klaver@xxxxxxxxxxx>> 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@xxxxxxxxxxx





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux