| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Sullivan <ajs(at)crankycanuck(dot)ca>, pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: postgresql idle |
| Date: | 2004-04-30 02:31:07 |
| Message-ID: | 200404300231.i3U2V8A06564@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alvaro Herrera wrote:
> > > Yeah. We agreed in principle awhile back to "fix" this on the backend
> > > side by postponing the actual transaction start until the first command
> > > after BEGIN. I looked at this just before 7.4 feature freeze, but
> > > decided it wasn't quite trivial and I hadn't time to make it happen.
> > > No one's gone back to work on it during the 7.5 cycle either.
> > >
> > > Right now I'm not wanting to touch that code since both Alvaro and the
> > > 2PC guy have open patches against it...
>
> Actually, my patch is waiting for you to review it ;-) On the other
> hand, since I'm already touching that code, maybe I can include it in my
> patch. Or would you prefer to keep those things separate?
Alvaro, can I ask what is left? I know you have pg_subtrans, but what
plans do you have to abort subtransactions and bring the system back to
the state before the subtransaction started?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2004-04-30 02:45:14 | Re: postgresql idle |
| Previous Message | Alvaro Herrera | 2004-04-30 02:27:57 | Re: postgresql idle |