| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: xlog location arithmetic |
| Date: | 2012-03-09 19:23:28 |
| Message-ID: | 1331321008.23681.2.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On fre, 2012-03-09 at 18:13 +0100, Magnus Hagander wrote:
> > and confusing XLogFileSize with XLogSegSize. Not the best choice of
> > names.
>
> Yeah, the use of XLogFile to mean something other than, well a file in
> the xlog, is greatly annoying.. I guess we could change it, but it
> goes pretty deep in the system so it's not a small change...
>
The whole thing was built around the lack of 64 bit integers. If we bit
the bullet and changed the whole thing to be just a single 64-bit
counter, we could probably delete thousands of lines of code.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-03-09 19:26:44 | Re: xlog location arithmetic |
| Previous Message | Robert Haas | 2012-03-09 19:16:25 | Re: Command Triggers, patch v11 |