From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Marek Więckowski <wieckom(at)foxi(dot)nl> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: auto-reconnect: temp schemas, sequences, transactions |
Date: | 2011-05-02 14:43:54 |
Message-ID: | 21240.1304347434@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Marek =?utf-8?q?Wi=C4=99ckowski?= <wieckom(at)foxi(dot)nl> writes:
> If I understand correctly, Tom's reply in:
> http://archives.postgresql.org/pgsql-general/2007-06/msg01668.php suggests
> that temp schemas are kept when a session gets disconnected because
> connections get automatically re-established with the same backend id, and if
> this succeeds the old temp tables get picked up by the new connection as if
> there was no disconnection at all.
Uh, no, surely not. The schema itself is re-used if it exists, but all
the contained tables get flushed by the new session (if for some reason
the old session failed to do that, as it would in case of a crash).
Re-use of the schema object is just a minor implementation optimization
--- there's no expectation that temp tables would ever survive into
another session.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Leif Biberg Kristensen | 2011-05-02 14:51:15 | Re: wnat ot edit pg_hba.conf file from command prompt |
Previous Message | Sim Zacks | 2011-05-02 14:28:48 | Re: wnat ot edit pg_hba.conf file from command prompt |