Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS

2018-04-04 Thread Gasper Zejn
On 04. 04. 2018 15:49, Bruce Momjian wrote: > I can understand why kernel developers don't want to keep failed sync > buffers in memory, and once they are gone we lose reporting of their > failure. Also, if the kernel is going to not retry the syncs, how long > should it keep reporting the sync

Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS

2018-04-09 Thread Gasper Zejn
On 09. 04. 2018 15:42, Tomas Vondra wrote: > On 04/09/2018 12:29 AM, Bruce Momjian wrote: >> An crazy idea would be to have a daemon that checks the logs and >> stops Postgres when it seems something wrong. >> > That doesn't seem like a very practical way. It's better than nothing, > of course, but

Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS

2018-04-21 Thread Gasper Zejn
Just for the record, I tried the test case with ZFS on Ubuntu 17.10 host with ZFS on Linux 0.6.5.11. ZFS does not swallow the fsync error, but the system does not handle the error nicely: the test case program hangs on fsync, the load jumps up and there's a bunch of z_wr_iss and z_null_int kernel

Re: community bonding

2018-04-23 Thread Gasper Zejn
ilable, but most of that can also be done in Eclipse. > > Also let me know if you have requirements in this phase which are not > covered by my plan.  > > Thanks Charles. A thing to note is that Postgres mailing lists are not top-post, so please try not to do that. Wiki is a gr

Re: pglz performance

2019-05-17 Thread Gasper Zejn
On 16. 05. 19 19:13, Andrey Borodin wrote: > >> 15 мая 2019 г., в 15:06, Andrey Borodin написал(а): >> >> Owners of AMD and ARM devices are welcome. I've tested according to instructions at the test repo https://github.com/x4m/test_pglz Test_pglz is at a97f63b and postgres at 6ba500. Hardware

Re: disable SSL compression?

2018-03-08 Thread Gasper Zejn
On 09. 03. 2018 06:24, Craig Ringer wrote: > I'm totally unconvinced by the threat posed by exploiting a client by > tricking it into requesting protocol compression - or any other > protocol change the client lib doesn't understand - with a connection > option in PGOPTIONS or the "options" connstr

Re: proposal: alternative psql commands quit and exit

2017-12-12 Thread Gasper Zejn
On 12. 12. 2017 06:58, Tom Lane wrote: > Craig Ringer writes: >> I doubt I've ever written just "exit" or "quit" without indentation. I >> think if it requires them to be a bareword with no indentation, strictly >> ^(exit|quit)\n when isatty, then that's probably a safe and helpful choice. > FWIW,