| From: | "John Wells" <jb(at)sourceillustrated(dot)com> |
|---|---|
| To: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "John Wells" <jb(at)sourceillustrated(dot)com>, "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Recovering data via raw table and field separators |
| Date: | 2007-12-04 20:05:53 |
| Message-ID: | 44dddf400712041205oaa69e5ax7e7e279e1f6b4aa@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 12/4/07, Martijn van Oosterhout <kleptog(at)svana(dot)org> wrote:
> Ah sorry, I though you meant de table was dropped or the database was
> deleted. If you actually ran a DELETE FROM on the table, then yes
> they'll all be marked deleted.
So, given a database table file that still has records in it, and
given the fact that these records could be parsed and displayed if the
proper utilty knew how to read the various data structures used to
denote field and record length, is there no utility to do this? I
seems that it would be fairly straight forward to somehow read the
records, yet to pay no mind to the deleted flag (or whatever mechanism
postgresql uses to mark them as deleted).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Obe, Regina | 2007-12-04 20:26:42 | Re: stored procedures and dynamic queries |
| Previous Message | Martijn van Oosterhout | 2007-12-04 19:47:58 | Re: Recovering data via raw table and field separators |