On 11/14/2011 03:47 PM, Kevin Grittner wrote:
This sounds like it might be another manifestation of something that
confused me a while back:
http://archives.postgresql.org/pgsql-hackers/2009-11/msg01754.php
http://archives.postgresql.org/pgsql-hackers/2009-12/msg00060.php
Interesting. That wa
Shaun Thomas wrote:
> Why on earth is it sending IN_CLOSE_WRITE messages for 0014, 1145,
> and 0061?
This sounds like it might be another manifestation of something that
confused me a while back:
http://archives.postgresql.org/pgsql-hackers/2009-11/msg01754.php
http://archives.postgresql.org
On 11/11/2011 04:21 PM, Shaun Thomas wrote:
So my real question: is this safe?
So to answer my own question: no, it's not safe. The PG backends
apparently write to the xlog files periodically and *close* them after
doing so. There's no open filehandle that gets written until the file is
ful
Hey guys,
I've been running some tests while setting up some tiered storage, and I
noticed something. Even having an empty 'echo' as archive_command
drastically slows down certain operations. For instance:
=> ALTER TABLE foo SET TABLESPACE slow_tier;
ALTER TABLE
Time: 3969.962 ms
When I set
