Understood, thanks. This is a new server fired up for our client by
Rackspace
Not real impressed so far, for the first several days we had major
performance issues even thought new new HW had more memory and
more/faster CPU's and faster IO - turned out rackspace had turned on cpu
throttling l
On Sun, Oct 23, 2016 at 12:45 PM, CS DBA wrote:
> would a dump/restore correct these issues?
Not directly, but it would give a logical representation of your data,
or a good start image that you could deploy on a server that has less
problems. You seem to be facing advanced issues with your hardw
also, any thoughts on what could be causing these issues?
On 10/22/2016 05:59 PM, Tom Lane wrote:
CS DBA writes:
So I ran REINDEX on all the db's and the errors went away for a bit. Now
I'm seeing this:
Log entries like this:FATAL: could not read block 0 of relation
base/1311892067/2687: rea
would a dump/restore correct these issues?
On 10/22/2016 05:59 PM, Tom Lane wrote:
CS DBA writes:
So I ran REINDEX on all the db's and the errors went away for a bit. Now
I'm seeing this:
Log entries like this:FATAL: could not read block 0 of relation
base/1311892067/2687: read only 0 of 81
CS DBA writes:
> So I ran REINDEX on all the db's and the errors went away for a bit. Now
> I'm seeing this:
> Log entries like this:FATAL: could not read block 0 of relation
> base/1311892067/2687: read only 0 of 8192 bytes
You have a problem there, because:
regression=# select 2687::regcla
So I ran REINDEX on all the db's and the errors went away for a bit. Now
I'm seeing this:
Log entries like this:FATAL: could not read block 0 of relation
base/1311892067/2687: read only 0 of 8192 bytes
So I checked which db it is:
$ psql -h localhost
psql (8.4.20)
Type "help" for help.
p
Thanks the REINDEX fixed it, it's a client of ours and we're pushing to
get them to move to 9.5
On 10/21/2016 06:33 PM, Tom Lane wrote:
CS DBA writes:
we're seeing the below errors over and over in the logs of one of our
postgres databases. Version 8.4.22
[ you really oughta get off 8.4, b
CS DBA writes:
> we're seeing the below errors over and over in the logs of one of our
> postgres databases. Version 8.4.22
[ you really oughta get off 8.4, but you knew that right? ]
> Anyone have any thoughts on correcting/debugging it?
> ERROR: xlog flush request 2571/9C141530 is not satis
Hi all;
we're seeing the below errors over and over in the logs of one of our
postgres databases. Version 8.4.22
Anyone have any thoughts on correcting/debugging it?
Maybe I need to run a REINDEX on whatever table equates to
"base/1029860192/1029863651"? If so how do I determine the db and
