(2013/08/02 21:19), Robert Haas wrote:
On Fri, Aug 2, 2013 at 8:17 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Jul 26, 2013 at 8:27 AM, Tom Lane t...@sss.pgh.pa.us wrote:
would you expect crash recovery to notice the disappearance of a file
that
On Fri, Jul 26, 2013 at 8:27 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Andres Freund and...@2ndquadrant.com writes:
On 2013-07-26 13:33:13 +0900, Satoshi Nagayasu wrote:
Is this expected or acceptable?
I'd say it's both.
Postgres is built on the assumption that the underlying filesystem is
Robert Haas robertmh...@gmail.com writes:
On Fri, Jul 26, 2013 at 8:27 AM, Tom Lane t...@sss.pgh.pa.us wrote:
would you expect crash recovery to notice the disappearance of a file
that was touched nowhere in the replayed actions?
Eh, maybe not. But should we try harder to detect the
On Fri, Aug 2, 2013 at 8:17 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Jul 26, 2013 at 8:27 AM, Tom Lane t...@sss.pgh.pa.us wrote:
would you expect crash recovery to notice the disappearance of a file
that was touched nowhere in the replayed
Hi,
I'm very new here on this mailing list, but I've been using PostgreSQL
for a while, and it scares me a little, that it's a real pain to try to
recover data from corrupted table.
Situations like file being lost following server crash (after fsck) or
page corruption happens quite often.
Hi Satoshi,
I was wondering about this problem. Please tell us about your system enviroment
which is postgresql version ,OS, raid card, and file system.
Best regards,
--
Mitsumasa KONDO
NTT Open Source Software Center
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To
Hi,
On 2013-07-26 13:33:13 +0900, Satoshi Nagayasu wrote:
I received a question about inconsistent state after crash recovery.
When a table file is broken (or just lost), PostgreSQL can not recover
a whole table, and does not show any notice while recoverying.
I think it means inconsistent
Andres Freund and...@2ndquadrant.com writes:
On 2013-07-26 13:33:13 +0900, Satoshi Nagayasu wrote:
Is this expected or acceptable?
I'd say it's both.
Postgres is built on the assumption that the underlying filesystem is
reliable, ie, once you've successfully fsync'd some data that data won't
Hi,
I received a question about inconsistent state after crash recovery.
When a table file is broken (or just lost), PostgreSQL can not recover
a whole table, and does not show any notice while recoverying.
I think it means inconsistent state.
(1) create a table, and fill records.
(2) process a
