| From: | Eduardo Morras <emorrasg(at)yahoo(dot)es> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: large table |
| Date: | 2014-09-22 19:47:01 |
| Message-ID: | 20140922214701.ab49958dc9ffda5a7848cc01@yahoo.es |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 22 Sep 2014 12:15:27 -0700
Luke Coldiron <lukecoldiron(at)hotmail(dot)com> wrote:
> > > I'd guess that some other process held a transaction open for a
> > > couple of week, and that prevented any vacuuming from taking
> > > place.
> > >
> Interesting idea, on the surface I'm not sure how this would have
> happened in the system but I can certainly explore forcing this to
> happen and see if the result is similar.
It happened when I developed with Java+Hibernate. It opened a transaction and made a lot of inserts and deletes while the app run. It created GB size tables with few rows and a permament 'IDLE in TRANSACTION' stops any autovacuum.
--- ---
Eduardo Morras <emorrasg(at)yahoo(dot)es>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bill Moran | 2014-09-22 20:27:58 | Re: large table |
| Previous Message | John R Pierce | 2014-09-22 19:46:21 | Re: large table |