pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedpg_restore error Command was: CREATE OPERATOR ~> ( PROCEDURE = plv8x.json_eval_ls,
4+ messages / 2 participants
[nested] [flat]
* pg_restore error Command was: CREATE OPERATOR ~> ( PROCEDURE = plv8x.json_eval_ls,
@ 2018-07-06 04:12 pavna <daryani.bhawna@gmail.com>
0 siblings, 1 reply; 4+ messages in thread
From: pavna @ 2018-07-06 04:12 UTC (permalink / raw)
To: pgsql-admin
When I pg_restore I get errors.
Postgres version : PostgreSQL 9.4.0 on x86_64-unknown-linux-gnu, compiled
by gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2, 64-bit
plv8.version : 1.5.0-dev1
pg_restore: processing item 2532 OPERATOR |
pg_restore: creating OPERATOR |
pg_restore: processing item 2533 OPERATOR |
pg_restore: creating OPERATOR |
pg_restore: processing item 2536 OPERATOR |>
pg_restore: creating OPERATOR |>
pg_restore: processing item 2537 OPERATOR |>
pg_restore: creating OPERATOR |>
pg_restore: [archiver (db)] Error from TOC entry 2537; 2617 27562 OPERATOR
|> employeeDB
pg_restore: [archiver (db)] could not execute query: ERROR: argument of
commutator must be a name
Command was: CREATE OPERATOR |> (
PROCEDURE = plv8x.json_eval,
LEFTARG = plv8x.json,
RIGHTARG = text,
COMMUTATOR = 27561
...
pg_restore: processing item 2534 OPERATOR ~
pg_restore: creating OPERATOR ~
pg_restore: processing item 2540 OPERATOR ~>
pg_restore: creating OPERATOR ~>
pg_restore: [archiver (db)] Error from TOC entry 2540; 2617 27566 OPERATOR
~> employeeDB
pg_restore: [archiver (db)] could not execute query: ERROR: argument of
commutator must be a name
Command was: CREATE OPERATOR ~> (
PROCEDURE = plv8x.json_eval_ls,
LEFTARG = plv8x.json,
RIGHTARG = text,
COMMUTATOR = 275...
pg_restore: processing item 2535 OPERATOR ~~
pg_restore: creating OPERATOR ~~
pg_restore: processing item 2670 OPERATOR CLASS gist__int_ops
pg_restore: creating OPERATOR CLASS gist__int_ops
pg_restore: processing item 347 TABLE account_setting
pg_restore: creating TABLE account_setting
pg_restore: processing item 348 SEQUENCE account_setting_id_seq
pg_restore: creating SEQUENCE account_setting_id_seq
pg_restore: processing item 4780 SEQUENCE OWNED BY account_setting_id_seq
pg_restore: creating SEQUENCE OWNED BY account_setting_id_seq
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: pg_restore error Command was: CREATE OPERATOR ~> ( PROCEDURE = plv8x.json_eval_ls,
@ 2018-07-06 16:20 Tom Lane <tgl@sss.pgh.pa.us>
parent: pavna <daryani.bhawna@gmail.com>
0 siblings, 1 reply; 4+ messages in thread
From: Tom Lane @ 2018-07-06 16:20 UTC (permalink / raw)
To: pavna <daryani.bhawna@gmail.com>; +Cc: pgsql-admin
pavna <daryani.bhawna@gmail.com> writes:
> When I pg_restore I get errors.
> pg_restore: [archiver (db)] could not execute query: ERROR: argument of
> commutator must be a name
> Command was: CREATE OPERATOR |> (
> PROCEDURE = plv8x.json_eval,
> LEFTARG = plv8x.json,
> RIGHTARG = text,
> COMMUTATOR = 27561
> ...
Seems like there's something broken in your source database, ie that
operator has a commutator link that didn't point to an existing operator.
Hard to say any more than that with no more information.
regards, tom lane
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: pg_restore error Command was: CREATE OPERATOR ~> ( PROCEDURE = plv8x.json_eval_ls,
@ 2018-07-06 17:08 pavna <daryani.bhawna@gmail.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 4+ messages in thread
From: pavna @ 2018-07-06 17:08 UTC (permalink / raw)
To: pgsql-admin
Thanks Tom for your response! Is there a way to examine the backup to find
what was missing?
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: pg_restore error Command was: CREATE OPERATOR ~> ( PROCEDURE = plv8x.json_eval_ls,
@ 2018-07-06 20:51 Tom Lane <tgl@sss.pgh.pa.us>
parent: pavna <daryani.bhawna@gmail.com>
0 siblings, 0 replies; 4+ messages in thread
From: Tom Lane @ 2018-07-06 20:51 UTC (permalink / raw)
To: pavna <daryani.bhawna@gmail.com>; +Cc: pgsql-admin
pavna <daryani.bhawna@gmail.com> writes:
> Thanks Tom for your response! Is there a way to examine the backup to find
> what was missing?
Well, it's whatever was the commutator for that operator. Evidently it
got dropped somewhere along the way.
It's a bit curious that you have this situation, though. AFAICS,
dropping an operator should result in clearing the oprcom link from
its commutator sibling. Perhaps there's some sequence of operations
that that logic fails to handle? It'd be interesting if you can show
a way to reproduce this case.
regards, tom lane
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2018-07-06 20:51 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2018-07-06 04:12 pg_restore error Command was: CREATE OPERATOR ~> ( PROCEDURE = plv8x.json_eval_ls, pavna <daryani.bhawna@gmail.com>
2018-07-06 16:20 ` Re: pg_restore error Command was: CREATE OPERATOR ~> ( PROCEDURE = plv8x.json_eval_ls, Tom Lane <tgl@sss.pgh.pa.us>
2018-07-06 17:08 ` Re: pg_restore error Command was: CREATE OPERATOR ~> ( PROCEDURE = plv8x.json_eval_ls, pavna <daryani.bhawna@gmail.com>
2018-07-06 20:51 ` Re: pg_restore error Command was: CREATE OPERATOR ~> ( PROCEDURE = plv8x.json_eval_ls, Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox