Re: DISCARD ALL (Again)
| От | David G Johnston |
|---|---|
| Тема | Re: DISCARD ALL (Again) |
| Дата | |
| Msg-id | CAKFQuwZA+UdPTpd3WgKZVg2EJCP7OBbVUMK-9TGsaBW71Efn+g@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: DISCARD ALL (Again) ("Joshua D. Drake" <jd@commandprompt.com>) |
| Ответы |
Re: DISCARD ALL (Again)
Re: DISCARD ALL (Again) |
| Список | pgsql-hackers |
On 04/17/2014 05:24 PM, Tom Lane wrote:> On the whole I'm not sure this is something we ought to get into.
> If you really need a fresh session, maybe you should start a
> fresh session.
Isn't the whole point to avoid the reconnection overhead, especially for connection poolers? DISCARD ALL shouldn't cause any cleanup that wouldn't otherwise occur when a session disconnects. True global data (not just session global) should be excluded.
A better wording of the promise would be: "discard all" leaves the session in the same state it would be in if the underlying connection were dropped and re-established.
David J.
View this message in context: Re: DISCARD ALL (Again)
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
В списке pgsql-hackers по дате отправления: