From: | "Marko Kreen" <markokr(at)gmail(dot)com> |
---|---|
To: | PGSQL-Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | RESET SESSION |
Date: | 2007-03-30 12:59:07 |
Message-ID: | e51f66da0703300559m595106f4t24719df91412b2b8@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
This is draft version, for discussion.
New commands:
CLOSE ALL
DEALLOCATE ALL
RESET PLANS
RESET TEMPS -- please suggest better name
RESET SESSION
So in the end RESET SESSION basically executes following commands:
ABORT;
DEALLOCATE ALL;
CLOSE ALL;
RESET ALL;
SET SESSION AUTHORIZATION DEFAULT;
UNLISTEN *;
RESET TEMPS;
RESET PLANS;
I think CLOSE ALL and DEALLOCATE ALL are useful in their own,
without considering poolers. They just make user lives easier.
The ALL just fits there.
RESET PLANS and RESET TEMPS are for the principle that components
for RESET SESSION should be available for users for special-case
situations and fine-tuning poolers. Also they add very little complexity.
(RESET PLANS could be useful its awn also).
Todo:
* Docs
* Disallow some commands inside TX?
* DEALLOCATE PREPARE ALL gives bison conflicts. is it needed?
* Send more details to client. Variants:
- CommandComplete: "RESET XXX", "CLOSE ALL", "DEALLOCATE ALL"
(CLOSE name and DEALLOCATE name would be good in normal case too,
that help anyone who wants to track what exists)
- RESET SESSION should send ParamStatus of all parms
--
marko
Attachment | Content-Type | Size |
---|---|---|
session.reset.diff | application/octet-stream | 12.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-03-30 13:44:28 | Re: DEALLOCATE ALL |
Previous Message | Peter Eisentraut | 2007-03-30 12:58:00 | Re: Current enums patch |