Hi there,
I am using a postgres 9.2 slave for some reports and I noticed that
sometimes they are held up because certain activity on the master like
vacuums can affect long queries on a slave .
Looking at pg_locks view , I can see that the recovering process on the
slave is holding some AccessExc
Update - someone unleashed a 'cleanup script' yesterday via puppet to
multiple hosts and greedily deleted files that had not been modified in 15
days. This is the most likely culprit so mystery basically solved.
Thankfully this is in QA, whew! It would be interesting to still know if
there are w
Alejandro Brust escribió:
> U could try some like "SET/ zero_damaged_pages = on"and perform a
> vacuum-db and may be pg_dump
I don't think this is a good idea. It might cause data loss. In any
case it's unlikely to fix the reported problem.
--
Álvaro Herrerahttp://www.2nd
El 04/10/2013 14:10, Mike Broers escribió:
> Strange, this is happening in a totally different environment now too.
> The only thing these two environments share is a SAN, but I wouldnt
> think something going on at the SAN level would make files disappear.
> Any suggestions are greatly apprecia
Strange, this is happening in a totally different environment now too. The
only thing these two environments share is a SAN, but I wouldnt think
something going on at the SAN level would make files disappear. Any
suggestions are greatly appreciated.
On Fri, Oct 4, 2013 at 9:40 AM, Mike Broers
El 04/10/2013 11:40, Mike Broers escribió:
> Hello, our postgresql 9.2.4 qa database (thankfully its just qa) seems
> to be hosed.
>
> Starting at around 3:39am last night I started seeing errors about
> missing files and now I cannot run a pgdump or a vacuum without it
> complaining about files
Hello, our postgresql 9.2.4 qa database (thankfully its just qa) seems to
be hosed.
Starting at around 3:39am last night I started seeing errors about missing
files and now I cannot run a pgdump or a vacuum without it complaining
about files that it cannot find with errors like this: ERROR: could
Radovan Jablonovsky wrote:
> When postgresql system tables, (tables in pg_catalog) reach size of 10mil
> rows, it will slow down some
> DDL operations, which insert, update or delete data from pg_* tables. Is it
> possible to partition the
> system tables or is there some other way to improve per
