| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ron <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_hba.conf is corrupt |
| Date: | 2018-08-24 22:48:46 |
| Message-ID: | 23736.1535150926@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Ron <ronljohnsonjr(at)gmail(dot)com> writes:
> completely overwritten by binary data. Been this way for 9 months, and we
> retain backups for 6 months.
> Is there any way to query postgres to regenerate this data?
Nope, sorry. PG doesn't ever write that file, and it doesn't keep spare
copies for you.
If you haven't shut down the postmaster, it's possible that you could
gdb into the postmaster (blocking connection attempts :-() and dig around
in the postmaster's data structures to reconstruct the info. But that's
probably impractical unless you have debug symbols for the server, and
even with that it'd be pretty tedious and easy to mess up.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Riou | 2018-08-25 07:04:14 | ERROR: no known snapshots |
| Previous Message | Ron | 2018-08-24 22:40:48 | pg_hba.conf is corrupt |