Re: [ADMIN] Postgres Server crashed

On Mon, Oct 10, 2011 at 2:59 PM, Kevin Grittner wrote: > Akash Kodibail wrote: > >> Can you please help me out in the options that might have to be >> set for pg_resetxlog. > > It should normally be able to calculate what it needs if you just > point it at the data directory.  I would run it with

Re: [ADMIN] Postgres Server crashed

Akash Kodibail wrote: > Can you please help me out in the options that might have to be > set for pg_resetxlog. It should normally be able to calculate what it needs if you just point it at the data directory. I would run it with the -n (no operation) flag first, to see what it plans to do.

Re: [ADMIN] Postgres Server crashed

Hi Scott, I believe pg_resetxlog has to have calculated and precise parameters: $PGDATA/pg_xlog has file -- 0001034A00C0 of 16Meg $PGDATA/pg_multixact/members has file -- of 8k $PGDATA/pg_multixact/offsets has file -- of 8k Can you please help me out in the options that mig

Re: [ADMIN] Postgres Server crashed

On Mon, Oct 10, 2011 at 1:13 PM, Akash Kodibail wrote: > I was hopeful of restoring the data from data files in $PGDATA path. I read > this article about PITR using the recovery.conf, But I am not aware of the > pre-requisites and not entirely sure about the concept beneath this. With PITR you

Re: [ADMIN] Postgres Server crashed

I was hopeful of restoring the data from data files in $PGDATA path. I read this article about PITR using the recovery.conf, But I am not aware of the pre-requisites and not entirely sure about the concept beneath this. Would it not be possible? Regards, Akash. -Original Message- From:

Re: [ADMIN] Postgres Server crashed

Scott Marlowe wrote: > Kevin Grittner wrote: > >> And normal maintenance may be viewing newer data as old, due to >> transaction wrap-around from the old pg_control file, and >> removing it as part of normal cleanup. So you may have destroyed >> some of your more recent data by doing that. > >

Re: [ADMIN] Postgres Server crashed

On Mon, Oct 10, 2011 at 11:17 AM, Kevin Grittner wrote: > And normal maintenance may be viewing newer data as old, due to > transaction wrap-around from the old pg_control file, and removing > it as part of normal cleanup.  So you may have destroyed some of > your more recent data by doing that.

Re: [ADMIN] Postgres Server crashed

Thank You Kevin. Details: --- Running "select version()" gives me "PostgreSQL 8.4.4 on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 3.4.6 20060404 (Red Hat 3.4.6-10), 64-bit" dmesg | head -10 -gives- "Linux version 2.6.18-92.el5 ([email protected]) (gcc version

Re: [ADMIN] Postgres Server crashed

kash Kodibail wrote: > Lately the postgres server crashed due to space constraints, The very first thing to do is to copy the entire directory structure for the database cluster to somewhere you can keep it safe until the problem has been resolved. If you have not yet done so, I strongly reco

[ADMIN] Postgres Server crashed

Hi All, I am a noob in database field. Lately the postgres server crashed due to space constraints, pg_control file got lost and the server wouldn't start. Had a old pg_control file placed in $PGDATA/global/ path. I was able to start the server, however, the data seems to be a very old one (2

Re: [ADMIN] [GENERAL] how to save a bytea value into a file?

On Mon, Oct 10, 2011 at 9:26 AM, Albe Laurenz wrote: > I wrote: > [fanlijing wants to write bytea to file] >> A simple >>    COPY (SELECT byteacol WROM mytab WHERE ...) TO 'filename' (FORMAT > binary) >> should do the trick. > > Corrections: > a) "binary" must be surrounded by single quotes. > b)

Re: [ADMIN] [GENERAL] how to save a bytea value into a file?

I wrote: [fanlijing wants to write bytea to file] > A simple >COPY (SELECT byteacol WROM mytab WHERE ...) TO 'filename' (FORMAT binary) > should do the trick. Corrections: a) "binary" must be surrounded by single quotes. b) that won't dump just the binary data - you would have to remove the

[ADMIN] pg_lesslog

Hi List What are your production experience with the pg_lesslog module, that compresses the WAL log? I would love to use it, but it would be nice with some reports of people having used it in production for some time... Thanks. -- Jesper -- Sent via pgsql-admin mailing list (pgsql-admin@pos

Re: [ADMIN] [GENERAL] how to save a bytea value into a file?

fanlijing wrote: > In Fact, I'm doing a porting project from Oracle 10g to PostgreSQL 9.0.4 > > There is a procedure in Oracle 10g to write a blob value into a file using: [...] > I know PostgreSQL doesn't support procedure, so I want to porting it into a > function use LANGUAGE plpgsql. > So I mu

[ADMIN] how to save a bytea value into a file?

Hello PostgreSQL members： I'm a user of PostgreSQL. Now I have a question when using it. When I want to save a bytea value into a file, what should I do？ Is there any function dealing with that in PostgreSQL? (like lo_export() to deal with the large-object) (# I didn't find any) Sorry for int

Re: [ADMIN] [GENERAL] how to save a bytea value into a file?

fanlijing wrote: > When I want to save a bytea value into a file, what should I do？ > Is there any function dealing with that in PostgreSQL? (like lo_export() to > deal with the large-object) (# I didn't find any) If you want to save it in a file on the server, you can use the COPY statement.