Rebecca Clarke wrote:
> On a side
> not, we're not doing a vacuumdb, but individual vacuum analyze statements on
> each table. Not sure if
> that makes any difference.
You vacuum the catalog tables as well, right?
Yours,
Laurenz Albe
--
Sent via pgsql-general mailing list (pgsql-general@postgr
Hi Jeff
Unfortunately it's not just the one particular query, there's no pattern
that I can see besides the time they're being executed.
We did go from Autovac only to nightly vac. I'm going to implement autovac
again, we've been operating without for a few months now. Will run both
nightly manua
On Mon, Apr 7, 2014 at 3:58 AM, Rebecca Clarke wrote:
> Thanks, I'll run the EXPLAIN (ANALYZE, BUFFERS) today and tomorrow
> morning. I just tried it now on a query that took 109035.116 ms this
> morning (Which returns one row). It has returned 675.496 ms. I will run
> on this same query at 5am t
On Mon, Apr 7, 2014 at 6:14 AM, Andrew Sullivan wrote:
> On Mon, Apr 07, 2014 at 10:32:59AM +0100, Rebecca Clarke wrote:
>
>> normally execute promptly, are taking a long time when they are executed
>> first thing in the morning (after the database has been inactive for
>> several hours). After th
On Mon, Apr 07, 2014 at 10:32:59AM +0100, Rebecca Clarke wrote:
> normally execute promptly, are taking a long time when they are executed
> first thing in the morning (after the database has been inactive for
> several hours). After the first execution, everything is back to normal.
Just guessin
Thanks, I'll run the EXPLAIN (ANALYZE, BUFFERS) today and tomorrow morning.
I just tried it now on a query that took 109035.116 ms this morning (Which
returns one row). It has returned 675.496 ms. I will run on this same query
at 5am tomorrow. Thank you.
At present we run pg_dumps every three hour
Rebecca Clarke wrote:
> I'm a bit stumped. At present I'm finding that queries to my database, that
> normally execute promptly,
> are taking a long time when they are executed first thing in the morning
> (after the database has been
> inactive for several hours). After the first execution, ever
On Mon, Apr 7, 2014 at 3:02 PM, Rebecca Clarke wrote:
> Hi all.
>
> I'm a bit stumped. At present I'm finding that queries to my database,
> that normally execute promptly, are taking a long time when they are
> executed first thing in the morning (after the database has been inactive
> for sever
Hi all.
I'm a bit stumped. At present I'm finding that queries to my database, that
normally execute promptly, are taking a long time when they are executed
first thing in the morning (after the database has been inactive for
several hours). After the first execution, everything is back to normal.
