NotificationsYou must be signed in to change notification settings
Fork5
Star26

Commitde479e2

committed

Revert part of the previous patch that avoided using PLy_elog().

That caused the plpython_unicode regression test to fail on SQL_ASCIIencoding, as evidenced by the buildfarm. The reason is that with the patch,you don't get the detail in the error message that you got before. Thatdetail is actually very informative, so rather than just adjust the expectedoutput, let's revert that part of the patch for now to make the buildfarmgreen again, and figure out some other way to avoid the recursion ofPLy_elog() that doesn't lose the detail.

1 parentb66de4c commitde479e2Copy full SHA for de479e2

File tree

1 file changed

-10

lines changed

src/pl/plpython
- plpy_util.c

1 file changed

-10

lines changed

`‎src/pl/plpython/plpy_util.c`

Lines changed: 1 addition & 10 deletions

Original file line number	Diff line number	Diff line change
`@@ -120,16 +120,7 @@ PLyUnicode_Bytes(PyObject *unicode)`
`120`	`120`
`121`	`121`	`rv=PyUnicode_AsEncodedString(unicode,serverenc,"strict");`
`122`	`122`	`if (rv==NULL)`
`123`		`-{`
`124`		`-/*`
`125`		`- * Use a plain ereport instead of PLy_elog to avoid recursion, if`
`126`		`- * the traceback formatting functions try to do unicode to bytes`
`127`		`- * conversion again.`
`128`		`- */`
`129`		`-ereport(ERROR,`
`130`		`-(errcode(ERRCODE_INTERNAL_ERROR),`
`131`		`-errmsg("could not convert Python Unicode object to PostgreSQL server encoding")));`
`132`		`-}`
	`123`	`+PLy_elog(ERROR,"could not convert Python Unicode object to PostgreSQL server encoding");`
`133`	`124`	`returnrv;`
`134`	`125`	`}`
`135`	`126`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commitde479e2

File tree

1 file changed

1 file changed

`‎src/pl/plpython/plpy_util.c`

0 commit comments