Normally, had their contents been deliberately encrypted we
understand you could have used the latest quantum computing
techniques to crack the code. But, since Dr. Shrum chose to use a
data format that had been lost in the winds of time, decipherment
proved impossible
Hmm... Let's see...
# cd /var/lib/postgres/data/pg_xlog
# strings 0000000000000011 | more
Serial
026324
Serial
5699K11353 cn 29L02
Roof fans Mfg
Greenheck
Roof fan serial
OOC23697
...
Looks like postgres (and, in my experience, most other
databases) stores its data internally as plain text unless
deliberately encrypted or compressed. Yeah, I'll give you
that
strings isn't likely to tell you the
structure of the data, but getting at the content without
going through the database engine is trivial.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
|
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.