| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: procpid? |
| Date: | 2011-06-09 17:18:30 |
| Message-ID: | 201106091718.p59HIUD06729@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas wrote:
> On Thu, Jun 9, 2011 at 11:54 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > Can someone explain why pg_stat_activity has a column named procpid and
> > not simply pid? ?'pid' is that pg_locks uses, and 'procpid' is redundant
> > (proc-process-id). ?A mistake?
>
> Well, we refer to the slots that backends use as "procs" (really
> PGPROC), so I'm guessing that this was intended to mean "the pid
> associated with the proc". It might not be the greatest name but I
> can't see changing it now.
Agreed. Just pointing out this mistake slipped through.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-06-09 17:22:42 | Re: Invalid byte sequence for encoding "UTF8", caused due to non wide-char-aware downcase_truncate_identifier() function on WINDOWS |
| Previous Message | Robert Haas | 2011-06-09 17:13:27 | Re: [v9.1] sepgsql - userspace access vector cache |