| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Russell Smith <mr-russ(at)pws(dot)com(dot)au> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: no XLOG during COPY? |
| Date: | 2008-09-16 10:05:32 |
| Message-ID: | 48CF84EC.6050505@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Russell Smith wrote:
> Andrew Dunstan wrote:
>
>> [snip]
>>
>>>
>>>
>> Er, who doesn't know what for certain, exactly? pg_restore will
>> certainly know that it has created the table in another session and
>> can thus safely truncate the table in the same transaction as the data
>> load.
>>
>> cheers
>>
>> andrew
>>
>>
> I'm confused about why table definition and data can't be loaded in the
> same backend and transaction. Can somebody explain that?
>
That would delay other things that depend on the table definition (e.g.
function definitions). If we don't need to make this link (and we don't)
then I can't see why we should shackle ourselves with it.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2008-09-16 10:26:17 | Re: [Review] fix dblink security hole |
| Previous Message | Martin Pihlak | 2008-09-16 10:00:53 | per-table autovacuum configuration |