| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Manuel Trujillo <manueltrujillo(at)dorna(dot)es> |
| Cc: | pg-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: stopping "wal" |
| Date: | 2002-02-12 15:16:19 |
| Message-ID: | 21480.1013526979@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Manuel Trujillo <manueltrujillo(at)dorna(dot)es> writes:
> When more or two or three processes are working, and I stop the
> database, if I have any problem stopping the DB, I kill the backends (is
> a tester machine).
This is a bad idea.
> When I start the process "postmaster", the wal make a "recover of
> processes", returning to the last situation.
> I would like to know how to "say" to postmaster don't make a "recover"
> from the wal files.
And this would be worse.
If you don't care about your data, you can "initdb" to get rid of the
messed-up database. If you do care, you shouldn't be doing any of the
above.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manuel Trujillo | 2002-02-12 15:57:51 | Re: stopping "wal" |
| Previous Message | Tom Lane | 2002-02-12 15:08:53 | Re: problem with view/function after upgrade to 7.2 |