[GENERAL] PostgreSQL on eMMC - Corrupt file system

Hi PostgreSQL experts, Today the root files system on my hardware running ubuntu was set to readonly, because the file system had some internal trouble. Output of `dmesg` is below. I am running owncloud with PostgreSQL on the hardware. What could be the root of this problem? It happened for

Re: [GENERAL] Logging broken messages

> On Feb 6, 2017, at 11:21 AM, Rui Pacheco wrote: > > I’m trying to implement a version of the wire protocol but I’ve hit a > problem: whenever I send a Close Statement message to the remote, it just > hangs indefinitely. I suspect the problem could be on my side but I

Re: [GENERAL] FATAL: remaining connection slots are reserved for non-replication superuser connections

2017-02-08 16:27 GMT+13:00 Tatsuo Ishii : > > Something is using too many connections. > > > > I may be wrong but I'm unaware of a limit on connections from PHP except > > when you are using persistent connections. Since each PHP script is it's > > own process, it can create

Re: [GENERAL] FATAL: remaining connection slots are reserved for non-replication superuser connections

> Something is using too many connections. > > I may be wrong but I'm unaware of a limit on connections from PHP except > when you are using persistent connections. Since each PHP script is it's > own process, it can create one or more connections. I'd check to be sure > that every PHP script you

Re: [GENERAL] FATAL: remaining connection slots are reserved for non-replication superuser connections

On Tue, Feb 7, 2017 at 6:52 PM, Patrick B wrote: > Hi guys, > > I get these messages at least once a day in my Prod environment: > >> FATAL: remaining connection slots are reserved for non-replication >> superuser connections > > I do not have a DB pooler and my

[GENERAL] FATAL: remaining connection slots are reserved for non-replication superuser connections

Hi guys, I get these messages at least once a day in my Prod environment: > FATAL: remaining connection slots are reserved for non-replication > superuser connections I do not have a DB pooler and my max_connections is 200. However, max connections for my PHP Application is 120. My server has

Re: [GENERAL] Logging broken messages

Steve Atkins writes: >> On Feb 6, 2017, at 9:21 AM, Rui Pacheco wrote: >> I’m trying to implement a version of the wire protocol but I’ve hit a >> problem: whenever I send a Close Statement message to the remote, it just >> hangs indefinitely. I

Re: [GENERAL] Logging broken messages

> On Feb 6, 2017, at 9:21 AM, Rui Pacheco wrote: > > Hello, > > I’m trying to implement a version of the wire protocol but I’ve hit a > problem: whenever I send a Close Statement message to the remote, it just > hangs indefinitely. I suspect the problem could be on my

[GENERAL] Logging broken messages

Hello, I’m trying to implement a version of the wire protocol but I’ve hit a problem: whenever I send a Close Statement message to the remote, it just hangs indefinitely. I suspect the problem could be on my side but I can’t find anything on my code that doesn’t match the manual

[GENERAL] Build exclusion constraints USING INDEX

Hi, I was wondering if there was any way to break down the creation of a new exclusion constraint into stages such that table locks most likely to affect performance during production hours are not taken. Something like: CREATE INDEX CONCURRENTLY new_index ON my_table USING gist (column1,