| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Joseph S <jks(at)selectacast(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: VACUUM and open transactions |
| Date: | 2007-01-31 01:55:19 |
| Message-ID: | 20070131015519.GD2178@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Joseph S wrote:
> I realize this thread is old, but I just conducted an experiment with pg
> 8.0.10 and a transaction with a SERIALIZABLE isolation level does
> prevent VACUUM from reclaiming rows that were created and then obsoleted
> in a subsequent transaction.
Right. This is expected. VACUUM cannot remove them because the
serializable transaction might still want to see those rows. (I am
assuming the serializable transaction is still running when the vacuum
starts. If that's not the case, please explain better).
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2007-01-31 02:15:01 | Re: Any Plans for cross database queries on the same server? |
| Previous Message | Joseph S | 2007-01-31 01:15:19 | Re: VACUUM and open transactions |