Re: Issue with PSQL JDBC Driver Null Pointer
Thanks for fixing it.
Thanks,
Bhavesh
On Thu, Jul 29, 2021 at 12:49 PM Dave Cramer
wrote:
>
>
> On Thu, 29 Jul 2021 at 15:44, Bhavesh Mistry
> wrote:
>
>> Hi Dave,
>>
>> It still does not address the NPE issue. If an alias is NULL. What
>> should be the behavior?
>>
>>
>> public String getTypeForAlias(String alias) {
>> String type = TYPE_ALIASES.get(alias);
>> if (type != null) {
>> return type;
>> }
>> type = TYPE_ALIASES.get(alias.toLowerCase()) *// NPE STILL HERE*;
>> if (type == null) {
>> type = alias;
>> }
>> //populate for future use
>> TYPE_ALIASES.put(alias, type);
>> return type;
>> }
>>
>
> Very good question. I guess we should return null in this case.
>
> I'll fix that
>
> Dave
>
--
Thanks,
Bhavesh
Postgres 9.6 to 12.7 pg_upgrade error - terminating connection due to administrator command
I am currently upgrading a Postgres cluster running on a Centos machine
from version 9.6.22 to 12.7. Post the install of 12.7 binaries, I am
running the pg_upgrade command:
/usr/pgsql-12/bin/pg_upgrade -b /usr/pgsql-9.6/bin/ -B /usr/pgsql-12/bin/
-d //9.6/data.old -D //12/data/ -j 12 -r -v -k
But, I am getting multiple errors during the "Restoring database schemas in
the new cluster" step:
pg_restore: creating TABLE "schema1.table1"
pg_restore: creating TABLE "schema1.table2"
pg_restore: creating TABLE "schema1.table3"
pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 358; 1259 793395 TABLE table3 postgres
pg_restore: error: could not execute query: FATAL: terminating
connection due to administrator command
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
Command was:-- For binary upgrade, must preserve pg_type oidSELECT
pg_catalog.binary_upgrade_set_next_pg_type_oid('793397'::pg_catalog.oid);
-- For binary upgrade, must preserve pg_type array oidSELECT
pg_catalog.binary_upgrade_set_next_array_pg_type_oid('793396'::pg_catalog.oid);
-- For binary upgrade, must preserve pg_class oidsSELECT
pg_catalog.binary_upgrade_set_next_heap_pg_class_oid('793395'::pg_catalog.oid);
CREATE TABLE "schema1"."table3" (
"date_key" integer NOT NULL,
"col1" character varying(32),
"col2" character varying(32),
"col3" character varying(32) NOT NULL
);
-- For binary upgrade, set heap's relfrozenxid and relminmxidUPDATE
pg_catalog.pg_classSET relfrozenxid = '1491955518', relminmxid =
'1'WHERE oid = '"schema1"."table3"'::pg_catalog.regclass;
Another log file:
pg_restore: creating TABLE "schema99.table1"
pg_restore: creating SEQUENCE "schema99.sequence1"
pg_restore: creating SEQUENCE OWNED BY "schema99.sequence1"
pg_restore: creating TABLE "schema99.table2"
pg_restore: creating SEQUENCE "schema99.sequence2"
pg_restore: creating SEQUENCE OWNED BY "schema99.sequence2"
pg_restore: creating SEQUENCE "schema99.sequence2"
pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 347; 1259 1949074 SEQUENCE sequence2 postgres
pg_restore: error: could not execute query: ERROR: relation
"sequence2" already exists
Command was:-- For binary upgrade, must preserve pg_class oidsSELECT
pg_catalog.binary_upgrade_set_next_heap_pg_class_oid('1949074'::pg_catalog.oid);
-- For binary upgrade, must preserve pg_type oidSELECT
pg_catalog.binary_upgrade_set_next_pg_type_oid('1949075'::pg_catalog.oid);
CREATE SEQUENCE "schema99"."sequence2"
START WITH 1
INCREMENT BY 1
NO MINVALUE
NO MAXVALUE
CACHE 1;
Restore command from the logs:
"/usr/pgsql-12/bin/pg_restore" --host /var/lib/pgsql --port 50432
--username postgres --create --exit-on-error --verbose --dbname
template1 "pg_upgrade_dump_16405.custom" >>
"pg_upgrade_dump_16405.log" 2>&1
Similarly, at each run a different dump file fails (
pg_upgrade_dump_16405.custom/pg_upgrade_dump_16404.custom). Has anyone
faced similar issues during upgrade to Postgres 12.7?
There isn't much in the pg_upgrade_server.log file. It looks like the
server starts and stops for the old and new data files.
pg_upgrade_server.log file - textuploader.com/ta9o3
Under //12/data/log. I see these lines:
```
LOG: background worker "logical replication launcher" (PID 35687) exited
with exit code 1
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2021-07-30 01:33:51 GMT
LOG: database system is ready to accept connections ERROR: relation
"sequence2" already exists
```
I am getting an error even after only initDB and running upgrade. Any
suggestions on what could be going wrong?
Thanks in advance!
Re: Postgres 9.6 to 12.7 pg_upgrade error - terminating connection due to administrator command
On Sat, Jul 31, 2021, 4:00 AM Dhanush D wrote:
> I am currently upgrading a Postgres cluster running on a Centos machine
> from version 9.6.22 to 12.7. Post the install of 12.7 binaries, I am
> running the pg_upgrade command:
>
> /usr/pgsql-12/bin/pg_upgrade -b /usr/pgsql-9.6/bin/ -B /usr/pgsql-12/bin/
> -d //9.6/data.old -D //12/data/ -j 12 -r -v -k
>
> But, I am getting multiple errors during the "Restoring database schemas
> in the new cluster" step:
>
> pg_restore: creating TABLE "schema1.table1"
> pg_restore: creating TABLE "schema1.table2"
> pg_restore: creating TABLE "schema1.table3"
> pg_restore: while PROCESSING TOC:
> pg_restore: from TOC entry 358; 1259 793395 TABLE table3 postgres
> pg_restore: error: could not execute query: FATAL: terminating connection
> due to administrator command
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> Command was:-- For binary upgrade, must preserve pg_type oidSELECT
> pg_catalog.binary_upgrade_set_next_pg_type_oid('793397'::pg_catalog.oid);
>
> -- For binary upgrade, must preserve pg_type array oidSELECT
> pg_catalog.binary_upgrade_set_next_array_pg_type_oid('793396'::pg_catalog.oid);
>
> -- For binary upgrade, must preserve pg_class oidsSELECT
> pg_catalog.binary_upgrade_set_next_heap_pg_class_oid('793395'::pg_catalog.oid);
> CREATE TABLE "schema1"."table3" (
> "date_key" integer NOT NULL,
> "col1" character varying(32),
> "col2" character varying(32),
> "col3" character varying(32) NOT NULL
> );
> -- For binary upgrade, set
>
>
> ```
> LOG: background worker "logical replication launcher" (PID 35687) exited
> with exit code 1
> LOG: shutting down
> LOG: database system is shut down
> LOG: database system was shut down at 2021-07-30 01:33:51 GMT
> LOG: database system is ready to accept connections ERROR: relation
> "sequence2" already exists
> ```
>
>
> I am getting an error even after only initDB and running upgrade. Any
> suggestions on what could be going wrong?
>
> Thanks in advance!
>
Just asking, is it possible for you to a schema dump from old db and
restore on the newer db, does it throw any errors.
If the db is not really big, maybe dump db with data and restore it on the
newer db server ( use the 12.x postgresql cli for dump restore)
If both these go through fine, then it would be easy to take any unrelated
ddl, data issues out to focus on pg_upgrade.
Re: Postgres 9.6 to 12.7 pg_upgrade error - terminating connection due to administrator command
On Friday, July 30, 2021, Dhanush D wrote: > > > pg_restore: error: could not execute query: FATAL: terminating connection > due to administrator command > > Did you control-C or something, maybe remote connection dropped? > pg_restore: creating SEQUENCE "schema99.sequence2" > pg_restore: creating SEQUENCE OWNED BY "schema99.sequence2" > pg_restore: creating SEQUENCE "schema99.sequence2" > > Is your source database corrupted such that this duplication appears in its catalog? David J.
