On Tue, Feb 28, 2017 at 5:07 AM, Magnus Hagander
wrote:
>
> server_log seems like a better choice then I think. So +1 for that.
>
server_log +1
>
> In theory cluster_log since it's a "cluster level log", but given how many
> people already get confused by the term cluster being used that w
Thanks tom, I confirm that ba61a04
<https://github.com/postgres/postgres/commit/ba61a04bc7fefeee03416d9911eb825c4897c223>
fixes
the issue. Now CI is passing.
Jorge Solórzano
me.jorsol.com
On Thu, Jan 19, 2017 at 6:09 PM, Tom Lane wrote:
> I wrote:
> > Hmm ... that line was
Yes, in fact it's a totally empty string:
https://github.com/pgjdbc/pgjdbc/blob/master/pgjdbc/src/main/java/org/postgresql/jdbc/PgConnection.java#L1317
Jorge Solórzano
me.jorsol.com
On Thu, Jan 19, 2017 at 3:57 PM, Tom Lane wrote:
> =?UTF-8?Q?Jorge_Sol=C3=B3rzano?= writes:
> &
__ = "ServerLoop"
> #5 0x007a6058 in PostmasterMain (argc=3, argv=0x2bac970) at
> postmaster.c:1320
> opt = -1
> status = 0
> userDoption = 0x2bce450 "/usr/local/pgsql/data"
> listen_addr_saved = 1 '\001'
>
[31742] FATAL: the database system is in
> recovery mode
> 2017-01-19 08:54:57.455 CST [31742] DEBUG: shmem_exit(1): 0
> before_shmem_exit callbacks to make
> 2017-01-19 08:54:57.455 CST [31742] DEBUG: shmem_exit(1): 0 on_shmem_exit
> callbacks to make
> 2017-01-19 08:54:
I have isolated the tests run by the pgjdbc project, I have disabled the
replication (wal_level = minimal) and the error is still present so it
seems that this error is not related to the replication, the test that
cause the error is AutoRollbackTestSuite, I have enable DEBUG mesages in
postgresql
