BUG #7511: 9.2: pg_stat_activity.procpid renamed unnecessarily
От | i@avdd.co |
---|---|
Тема | BUG #7511: 9.2: pg_stat_activity.procpid renamed unnecessarily |
Дата | |
Msg-id | E1T6wSQ-0005kN-LD@wrigleys.postgresql.org обсуждение исходный текст |
Ответы |
Re: BUG #7511: 9.2: pg_stat_activity.procpid renamed unnecessarily
Re: BUG #7511: 9.2: pg_stat_activity.procpid renamed unnecessarily |
Список | pgsql-bugs |
The following bug has been logged on the website: Bug reference: 7511 Logged by: Adrian Dries Email address: i@avdd.co PostgreSQL version: Unsupported/Unknown Operating system: any Description: = In trying 9.2 I find pg_stat_activity.procpid has been renamed to pid. http://git.postgresql.org/gitweb/?p=3Dpostgresql.git;a=3Dcommitdiff;h=3D4f4= 2b546fd87a80be30c53a0f2c897acb826ad52 It seems the premise of this is If we're going to rename current_query to query--what Scott's patch does here--that will force all code using pg_stat_activity to be rewritten. This seems like the perfect time to also change "procpid" to "pid", finally blow away that wart. A premise that is untrue: changing a subset of columns on a relation does not force "all code" using that relation to be rewritten: SELECT procpid FROM pg_stat_activity WHERE procpid <> pg_backend_pid()
В списке pgsql-bugs по дате отправления: