Hi,
We have just upgraded our Postgres 9.6 database to 12.1 (pg_dumpall ->
pg_restore on a clean installation) and now we are having some issues
with one of our tables.
When we do the following statement:
SELECT * FROM f_gsxws_schedule WHERE UPPER(gwsc_dossier) = 'TEST'
the Postgres
On 2/8/20 12:09 PM, Nick Renders wrote:
Hi,
We have just upgraded our Postgres 9.6 database to 12.1 (pg_dumpall ->
pg_restore on a clean installation) and now we are having some issues
with one of our tables.
When we do the following statement:
SELECT * FROM f_gsxws_schedule WHERE UPPE
Adrian,
Everything was a clean install ( MacOS Mojave and Postgres )
Export and import were done with the latest version of PGAdmin.
Please advise if we can provide you with anything ( logging etc . . . )
Is there a possibility to downgrade to version 11 ?
We upgraded over the weekend becaus
On 2/8/20 12:28 PM, Marc wrote:
Adrian,
Everything was a clean install ( MacOS Mojave and Postgres )
Export and import were done with the latest version of PGAdmin.
Please advise if we can provide you with anything ( logging etc . . . )
Is there a possibility to downgrade to version 11 ?
A
Adrian,
Old production server was postgres 9.6 with Mac0S 10.9 so much older
than the “new” server. ( Now MacOS 10.14 Postgres 12.1 )
After sudden restart of the cpu we started having issues, part of the
data that is lost TOAST. . . and we also started having issues when
TRUNCATING certain ta
## Nick Renders (postg...@arcict.com):
> 2020-02-08 20:21:19.942 CET [83892] LOG: server process (PID 85456)
> was terminated by signal 9: Killed: 9
Signal 9 sounds like OOM (or manual intervention). What's in dmesg?
Regards,
Christoph
--
Spare Space
"Nick Renders" writes:
> When we do the following statement:
> SELECT * FROM f_gsxws_schedule WHERE UPPER(gwsc_dossier) = 'TEST'
> the Postgres service restarts.
Hm.
> Here is what is logged:
> 2020-02-08 20:21:19.942 CET [83892] LOG: server process (PID 85456) was
> terminated by signal
On 2/8/20 2:24 PM, Marc wrote:
Adrian,
Old production server was postgres 9.6 with Mac0S 10.9 so much older
than the “new” server. ( Now MacOS 10.14 Postgres 12.1 )
After sudden restart of the cpu we started having issues, part of the
data that is lost TOAST. . . and we also started having iss