[ADMIN] Data corruption / recover

2013-02-28 Thread Daniel Paval
Hi, We're dealing with the following situation (PG version is 7.4.30): somehow, a DB has gone missing from pg_database (psql \l listing doesn't show it anymore). More, while you can still \c to it, a \d table listing only shows a fraction of the tables. A \d on the existing tables shows missi

Re: [ADMIN] Data corruption / recover

2013-02-28 Thread Tom Lane
Daniel Paval writes: > We're dealing with the following situation (PG version is 7.4.30): 7.4? I sure hope you're going to migrate onto something less obsolete once you get out of this problem. In any still-in-support release series, autovacuum would have saved you from this. > somehow, a DB

Re: [ADMIN] Data corruption / recover

2013-02-28 Thread Scott Marlowe
On Thu, Feb 28, 2013 at 7:21 AM, Tom Lane wrote: > Daniel Paval writes: >> We're dealing with the following situation (PG version is 7.4.30): > > 7.4? I sure hope you're going to migrate onto something less obsolete > once you get out of this problem. In any still-in-support release > series, a

Re: [ADMIN] Data corruption / recover

2013-02-28 Thread Daniel Paval
On 28.02.2013 18:48, Scott Marlowe wrote: On Thu, Feb 28, 2013 at 7:21 AM, Tom Lane wrote: Daniel Paval writes: We're dealing with the following situation (PG version is 7.4.30): 7.4? I sure hope you're going to migrate onto something less obsolete once you get out of this problem. In any

[ADMIN] Assistance with libpq

2013-02-28 Thread Jesse Johnson
Hello, I have an issue that is driving me crazy. I am using libpq on linux in C. The insert code below inserts one key/data pair record with as both as BYTEA into database test2: PGresult* put_data_to_test2(PGconn* conn, int key_size, const char* const key, int data_size, const char* const data)