| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Alessandro Baretta <a(dot)baretta(at)barettadeit(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Suspending SELECTs |
| Date: | 2006-01-16 18:10:38 |
| Message-ID: | 9997.1137435038@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> I wonder if we could have a way to "suspend" a transaction and restart
> it later in another backend. I think we could do something like this
> using the 2PC machinery.
> Not that I'm up for coding it; just an idea that crossed my mind.
It's not impossible, perhaps, but it would require an order-of-magnitude
expansion of the 2PC machinery --- the amount of state associated with
an open execution plan is daunting. I think there are discussions about
this in the archives.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Lewis | 2006-01-16 18:45:09 | Re: Suspending SELECTs |
| Previous Message | Alvaro Herrera | 2006-01-16 17:57:38 | Re: Suspending SELECTs |