| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Hanns Hartman <hwhartman(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: How is autovacuum affected by a change in year. |
| Date: | 2015-02-26 16:02:29 |
| Message-ID: | 776.1424966549@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hanns Hartman <hwhartman(at)gmail(dot)com> writes:
> I am running postgres 8.3.17 on a RedHat linux derivative using a mips64
> architecture.
You realize of course that 8.3 is long out of support ...
> I've recently noticed some odd autovacuum behavior.
> Recently we've had some systems deployed with the system clock set to the
> year 2016. Postgres was installed with that date and things were fine
> until a user noticed the incorrect date. They reset the system time back
> to 2015 and then we started seeing weird behavior where the autovacuum
> proccess does not seem to be maintaining the disk space.
I would not be surprised if the autovacuum launcher thinks that it doesn't
need to touch that database again until 2016. A quick DB restart should
fix it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Smith | 2015-02-26 16:03:51 | Re: "JSON does not support infinite date values" |
| Previous Message | Neil Tiffin | 2015-02-26 15:59:19 | Re: Create Virtual Indexes on Postgres |