![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I found out that activating log_parser_stats = true log_planner_stats = true log_executor_stats = true log_statement_stats = true in postgresql.conf leads to this bug |
#3
| |||
| |||
|
|
Martin Pitt <martin (AT) piware (DOT) de> writes: I found out that activating =20 log_parser_stats =3D true log_planner_stats =3D true log_executor_stats =3D true log_statement_stats =3D true =20 in postgresql.conf leads to this bug =20 This is another manifestation of the 7.4 problem with trying to test superuser-ness at inappropriate times. We eventually gave up on the entire concept of "USERLIMIT" variables. I don't think there is any reasonably practical patch to fix it in 7.4, sorry ... |
![]() |
| Thread Tools | |
| Display Modes | |
| |