Tom Lane wrote:
> Rodrigo Gonzalez <[EMAIL PROTECTED]> writes:
>> pg_dump is working fine now, the problem appear with the pg_buffercache
>> query...without it I dont notice anything wrong with DBbut of course
>> there is something wrong. Can be pg_buffercache the problem?
>
> Oh ... looking a
Rodrigo Gonzalez <[EMAIL PROTECTED]> writes:
> pg_dump is working fine now, the problem appear with the pg_buffercache
> query...without it I dont notice anything wrong with DBbut of course
> there is something wrong. Can be pg_buffercache the problem?
Oh ... looking again at your latest probl
Rodrigo Gonzalez <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> When you say "restored from backup", are you talking about a pg_dump
>> backup, or what?
> yes, a pg_dump backup.
There must be something mighty odd in that backup. Would you be willing
to send it to me off-list, so I can try to r
Alban Hertroys wrote:
> On Jun 26, 2008, at 5:41 AM, Rodrigo Gonzalez wrote:
>
>> Tom Lane wrote:
>>> Rodrigo Gonzalez <[EMAIL PROTECTED]> writes:
Craig Ringer wrote:
> What platform are you using?
>>>
It's running under CentOS 4.4 using ext3, no RAID or LVM.
Server is quad xeon
Tom Lane wrote:
> Rodrigo Gonzalez <[EMAIL PROTECTED]> writes:
>> Tom Lane wrote:
>>> No, it's clear that things are already broken before pg_dump started.
>>> You need to show us how to get to this state from a fresh database.
>
>> Interestinga new problem maybe, or maybe the same one
>>
Rodrigo Gonzalez <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> No, it's clear that things are already broken before pg_dump started.
>> You need to show us how to get to this state from a fresh database.
> Interestinga new problem maybe, or maybe the same one
> ...
> ERROR: relation "p
On Jun 26, 2008, at 5:41 AM, Rodrigo Gonzalez wrote:
Tom Lane wrote:
Rodrigo Gonzalez <[EMAIL PROTECTED]> writes:
Craig Ringer wrote:
What platform are you using?
It's running under CentOS 4.4 using ext3, no RAID or LVM.
Server is quad xeon 64 bits 3 GHz
Ugh, I'd have liked to think RHEL
Tom Lane wrote:
> Rodrigo Gonzalez <[EMAIL PROTECTED]> writes:
>> Dont know exactly what you mean, if you are talking about the moment
>> that I receive the error...
>
> No, it's clear that things are already broken before pg_dump started.
> You need to show us how to get to this state from a fres
Rodrigo Gonzalez <[EMAIL PROTECTED]> writes:
> Dont know exactly what you mean, if you are talking about the moment
> that I receive the error...
No, it's clear that things are already broken before pg_dump started.
You need to show us how to get to this state from a fresh database.
Tom Lane wrote:
> Rodrigo Gonzalez <[EMAIL PROTECTED]> writes:
>> Basically I should reinstall again PG with the same configuration and
>> wait 1 night. Any log you need or want? anything to do besides doing the
>> same I did?
>
> Umm ... if I reinstall PG and wait one night, I'm quite sure that
>
Rodrigo Gonzalez <[EMAIL PROTECTED]> writes:
> Basically I should reinstall again PG with the same configuration and
> wait 1 night. Any log you need or want? anything to do besides doing the
> same I did?
Umm ... if I reinstall PG and wait one night, I'm quite sure that
nothing much will happen.
Tom Lane wrote:
> Rodrigo Gonzalez <[EMAIL PROTECTED]> writes:
>> Craig Ringer wrote:
>>> What platform are you using?
>
>> It's running under CentOS 4.4 using ext3, no RAID or LVM.
>> Server is quad xeon 64 bits 3 GHz
>
> Ugh, I'd have liked to think RHEL4/Centos4 would be more reliable than
> t
Tom Lane wrote:
> Rodrigo Gonzalez <[EMAIL PROTECTED]> writes:
>> Tom Lane wrote:
>>> Did you update anything else at the same time?
>
>> No, just postgres was updated
>
> Well, that does start to sound like it could be a PG bug; but no one
> else is reporting anything like it. Can you put toget
Tom Lane wrote:
> Rodrigo Gonzalez <[EMAIL PROTECTED]> writes:
>> It had been working with pgsql 8.1 and 8.2 for 2 years without problems.
>> Suspicious is that problems started next day I've upgraded to 8.3.
>
> Did you update anything else at the same time?
>
> regards, to
Rodrigo Gonzalez <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Did you update anything else at the same time?
> No, just postgres was updated
Well, that does start to sound like it could be a PG bug; but no one
else is reporting anything like it. Can you put together a
self-contained test cas
Rodrigo Gonzalez <[EMAIL PROTECTED]> writes:
> It had been working with pgsql 8.1 and 8.2 for 2 years without problems.
> Suspicious is that problems started next day I've upgraded to 8.3.
Did you update anything else at the same time?
regards, tom lane
--
Sent via pgsql
Rodrigo Gonzalez <[EMAIL PROTECTED]> writes:
> Craig Ringer wrote:
>> What platform are you using?
> It's running under CentOS 4.4 using ext3, no RAID or LVM.
> Server is quad xeon 64 bits 3 GHz
Ugh, I'd have liked to think RHEL4/Centos4 would be more reliable than
that :-(. Still, you might hav
Tom Lane wrote:
> Rodrigo Gonzalez <[EMAIL PROTECTED]> writes:
>> PgSQL is returning that error when I open pgdmin and when I run some
>> queries related to pg_buffercache. Also pg_dump cannot dump the DB.
>> PgSQL version is 8.3.3 and happened one day after loading the DB there.
>
> That raises a
Craig Ringer wrote:
> Rodrigo Gonzalez wrote:
>> PgSQL is returning that error when I open pgdmin and when I run some
>> queries related to pg_buffercache. Also pg_dump cannot dump the DB.
>>
>> PgSQL version is 8.3.3 and happened one day after loading the DB there.
>
> What platform are you using
Rodrigo Gonzalez <[EMAIL PROTECTED]> writes:
> PgSQL is returning that error when I open pgdmin and when I run some
> queries related to pg_buffercache. Also pg_dump cannot dump the DB.
> PgSQL version is 8.3.3 and happened one day after loading the DB there.
That raises a lot of questions about t
Rodrigo Gonzalez wrote:
> PgSQL is returning that error when I open pgdmin and when I run some
> queries related to pg_buffercache. Also pg_dump cannot dump the DB.
>
> PgSQL version is 8.3.3 and happened one day after loading the DB there.
What platform are you using?
If Windows:
- Which vers
PgSQL is returning that error when I open pgdmin and when I run some
queries related to pg_buffercache. Also pg_dump cannot dump the DB.
PgSQL version is 8.3.3 and happened one day after loading the DB there.
Anything that can be done? or I have to restore a backup and put current
data again?
Th
22 matches
Mail list logo
