| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru> |
| Cc: | Grigory Smolkin <g(dot)smolkin(at)postgrespro(dot)ru>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: fun fact about temp tables |
| Date: | 2016-08-05 15:54:22 |
| Message-ID: | 17134.1470412462@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru> writes:
> On 05.08.2016 17:51, Tom Lane wrote:
>> Sure. Just like it reserves space for ordinary tables right away,
>> long before there's any need to push the data out of shared_buffers.
>> Otherwise, you might find yourself having to throw an "out of disk
>> space" error after having already committed the relevant INSERTs.
> How about out of space when we filling WAL files?
What about it? That will be reported before committing, too.
What Grigory wants would imply committing and then sometime later
saying "oh, wait ... remember that data we told you we'd committed?
We lied."
Temp tables do indeed disappear at session end (and a fortiori after
a crash), but that doesn't create an excuse for them not to have
normal transactional behavior within the session.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Grigory Smolkin | 2016-08-05 15:59:27 | Re: fun fact about temp tables |
| Previous Message | Tom Lane | 2016-08-05 15:50:47 | Re: fun fact about temp tables |