Skip site navigation (1) Skip section navigation (2)

Re: Large transaction problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Paul B(dot) Anderson" <paul(at)pnlassociates(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Large transaction problem
Date: 2004-11-11 22:48:52
Message-ID: 12504.1100213332@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
"Paul B. Anderson" <paul(at)pnlassociates(dot)com> writes:
> After I restart postgresql, I execute vacuum several times in sql until 
> it succeeds.  Then, everything else works OK again.
> After I clear the problem,
>   select count(*) from archive
> takes a second but, before the problem is cleared, it takes about 30 
> seconds and then gives the canceled by user response.

This all sounds exactly like an overly enthusiastic statement_timeout.
What you are doing to "clear the problem" is merely to populate the disk
cache sufficiently that your query finishes before timing out.

			regards, tom lane

In response to

pgsql-admin by date

Next:From: Francisco Jose Bernabe PellicerDate: 2004-11-12 14:14:33
Subject: Query failed: ERROR: Unable to identify an operator '=' for types 'character varying' and 'character'
Previous:From: Paul B. AndersonDate: 2004-11-11 22:14:50
Subject: Re: Large transaction problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group