Tom Lane wrote:
Jesse Cleary <[EMAIL PROTECTED]> writes:
This script has been running successfully for several months (70-90 min each
night). Out of the blue I'm now getting the following error message after each
psql command, except the last vacuum full analyze command:
ERROR: could not
Jesse Cleary <[EMAIL PROTECTED]> writes:
> This script has been running successfully for several months (70-90 min each
> night). Out of the blue I'm now getting the following error message after
> each psql command, except the last vacuum full analyze command:
> ERROR: could not create relatio
Jesse Cleary <[EMAIL PROTECTED]> writes:
> One exception is notable - $PGDATA/base/835021/4294967264 - this file
> has a size of 0 and a timestamp that coincides with the date and time
> range of the nightly run when these errors first appeared. This seems
> like a good clue, but not sure what
Tom Lane wrote:
Jesse Cleary <[EMAIL PROTECTED]> writes:
This script has been running successfully for several months (70-90 min each
night). Out of the blue I'm now getting the following error message after each
psql command, except the last vacuum full analyze command:
ERROR:
Jesse Cleary <[EMAIL PROTECTED]> writes:
> This script has been running successfully for several months (70-90 min each
> night). Out of the blue I'm now getting the following error message after
> each psql command, except the last vacuum full analyze command:
> ERROR: could not create relati
Hi PG Listers,
Postgres newbie here with a DB maintenance problem. I'm running a nightly
maintenance script on a PG database with ~50 tables and ~2.8 million rows
distributed rather unevenly across those tables. It is updated hourly with
7-10k new rows per hour.
Every night I run a bash scr
