Re: [GENERAL] pg_dump in stand alone backend

Ulrich Wisser <[EMAIL PROTECTED]> writes: > I need to to disconnect any other users and do "vacuum full verbose > analyze" "reindex database" and reindex all tables. And for these I will > stop the postmaster and run a stand alone backend. I think the real problem here is stone-age maintenance p

Re: [GENERAL] pg_dump in stand alone backend

Ulrich Wisser wrote: Hi, I would like to stop the postmaster every night and run vacuum pg_dump reindex in the stand alone backend. Vacuum and reindex seem to be quite easy, as I can setup a small script with both commands. But what about pg_dump. That seems "somewhat" more complex. Explain what

Re: [GENERAL] pg_dump in stand alone backend

Daniel Martini wrote: Hi, Citing Ulrich Wisser <[EMAIL PROTECTED]>: I would like to stop the postmaster every night and run vacuum pg_dump reindex in the stand alone backend. Vacuum and reindex seem to be quite easy, as I can setup a small script with both commands. But what about pg_dump. That se

Re: [GENERAL] pg_dump in stand alone backend

Hi, Citing Ulrich Wisser <[EMAIL PROTECTED]>: > I would like to stop the postmaster every night and run > > vacuum > pg_dump > reindex > > in the stand alone backend. > > Vacuum and reindex seem to be quite easy, as I can setup a small script > with both commands. But what about pg_dump. That

[GENERAL] pg_dump in stand alone backend

Hi, I would like to stop the postmaster every night and run vacuum pg_dump reindex in the stand alone backend. Vacuum and reindex seem to be quite easy, as I can setup a small script with both commands. But what about pg_dump. That seems "somewhat" more complex. TIA Ulrich --