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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
