| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Jim Nasby <jim(at)nasby(dot)net>, Jeff Amiel <becauseimjeff(at)yahoo(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_rewarm status |
| Date: | 2013-12-19 14:25:15 |
| Message-ID: | 20131219142515.GB11483@alap2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-12-19 09:16:59 -0500, Robert Haas wrote:
> There's no uint32 type at the SQL level, and int32 is no good because
> it can't represent sufficiently large positive values to cover the
> largest possible block number.
Well, pg_class.relpages is an int32, so I think that limit is already
kind of there, even though BlockNumber is typedef'ed to uint32. Yes, we
should rectify that sometime.
Even so, I don't see a reason not to use int64 here, before that.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-12-19 14:37:09 | Re: preserving forensic information when we freeze |
| Previous Message | Andres Freund | 2013-12-19 14:19:14 | Re: preserving forensic information when we freeze |