| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Silvela, Jaime \(Exchange\)" <JSilvela(at)Bear(dot)com> |
| Cc: | "pgsql-general" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Can't open Postgres at all!!! |
| Date: | 2006-08-24 14:43:54 |
| Message-ID: | 4705.1156430634@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Silvela, Jaime \(Exchange\)" <JSilvela(at)Bear(dot)com> writes:
>> If the index entries for the system catalogs themselves are hosed,
>> you may have to start the session with PGOPTIONS="-P" (to disable
>> trusting system indexes) in order to do REINDEX successfully.
> Excuse my ignorance, how do I do that. Linux env setting? Is it a
> command line option for Postmaster?
Originally it was only a postmaster command line option, but since about
7.4 you can set it in psql's environment, and that's what I'd recommend
for a one-shot repair effort.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-08-24 14:50:27 | Re: getting around 'out of memory' errors |
| Previous Message | Ron Johnson | 2006-08-24 14:18:07 | Re: Length limit for query |