| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Gregory Stark <gsstark(at)mit(dot)edu> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Matteo Sgalaberni <sgala(at)sgala(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: database bloat, non removovable rows, slow query etc... [RESOLVED] |
| Date: | 2006-09-04 22:47:16 |
| Message-ID: | 20060904224716.GB14107@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Gregory Stark wrote:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>
> > Matteo Sgalaberni <sgala(at)sgala(dot)com> writes:
> > > Good to know this...but why this behaviour? it'is lovely...:)
> >
> > Open transactions are tracked across the whole cluster. This is
> > necessary when vacuuming shared catalogs. In principle we could
> > track per-database xmin values as well, but the distributed overhead
> > that'd be added to *every* GetSnapshotData call is a bit worrisome.
>
> Don't we do that now in CVS (ie, in 8.2)?
No, we don't.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2006-09-05 00:30:15 | Re: database bloat, non removovable rows, slow query etc... [RESOLVED] |
| Previous Message | Gregory Stark | 2006-09-04 22:13:34 | Re: database bloat, non removovable rows, slow query etc... [RESOLVED] |