| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Log timestamps at higher resolution |
| Date: | 2018-10-25 16:22:50 |
| Message-ID: | 20181025162250.xvcu7z7bsno757yr@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018-Oct-25, David Fetter wrote:
> > I didn't intend to add anything else later. I don't think we have
> > any variables that zero padding would be that useful for, but maybe
> > someone might want to zero pad their pids or xids... ?
>
> They might, so I'll either put in a comment where that would go or
> just implement it.
I've never seen a need for zero-padding XIDs or PIDs, frankly. Can you
imagine the mess if we ever grew XIDs to 64 bits? And what about
OS-level configurability of PIDs? I don't know that there's a good way
to learn their widths.
I don't think it's worth of a comment even.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2018-10-25 17:06:30 | Re: libpq host/hostaddr/conninfo inconsistencies |
| Previous Message | David Fetter | 2018-10-25 16:04:22 | Re: Log timestamps at higher resolution |