| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Joseph S <jks(at)selectacast(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: VACUUM and open transactions |
| Date: | 2006-10-19 20:49:28 |
| Message-ID: | 20061019204928.GE13348@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Oct 19, 2006 at 04:25:09PM -0400, Joseph S wrote:
> >The problem is that the "old" transaction can see effects of later
> >started transactions, so VACUUM can't delete the later stuff either...
>
> How can it see effects of transactions that started after it?
Check the documentation for the difference the READ COMMITTED and
SERIALIZABLE transaction. The former (the default) will see the results
of any committed transactions, even if they started later.
http://www.postgresql.org/docs/8.1/interactive/transaction-iso.html#XACT-READ-COMMITTED
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Casey Duncan | 2006-10-19 21:35:47 | Re: Help needed |
| Previous Message | Joseph S | 2006-10-19 20:25:09 | Re: VACUUM and open transactions |