From: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: DISCARD ALL (Again) |
Date: | 2014-04-20 02:15:13 |
Message-ID: | CAFcNs+p0Ro3oWC+H1+16yLVawj=SvCP=ztor9Fcc1OmSc1BH5A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Apr 18, 2014 at 12:00 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>
> On 4/17/14, 8:24 PM, Tom Lane wrote:
> > We could in fact implement #2, I imagine, by destroying and recreating
> > the entire language interpreter. So I could imagine implementing a
> > "DISCARD INTERPRETERS" kind of command that would zap the current
> > interpreter(s) for whichever PL languages happened to feel like
> > cooperating with the command.
>
> More generally, any extension could maintain any kind of cross-call
> state. plproxy, dblink, pgmemcache come to mind. A general hook into
> DISCARD might be doable, but then it's not clear how to categorize this
> into DISCARD subcommands.
>
I proposed some like that in a previous message [1].
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
From | Date | Subject | |
---|---|---|---|
Next Message | Palle Girgensohn | 2014-04-20 09:24:38 | Perfomance degradation 9.3 (vs 9.2) for FreeBSD |
Previous Message | Bruce Momjian | 2014-04-20 01:22:33 | Re: Avoiding deeply nested AND/OR trees in the parser |