Re: pg_class.relpages/allvisible probably shouldn't be a int4
| От | Andres Freund |
|---|---|
| Тема | Re: pg_class.relpages/allvisible probably shouldn't be a int4 |
| Дата | |
| Msg-id | 20140530110351.GD25431@alap3.anarazel.de обсуждение |
| Ответ на | Re: pg_class.relpages/allvisible probably shouldn't be a int4 (Simon Riggs <simon@2ndQuadrant.com>) |
| Список | pgsql-hackers |
On 2014-05-30 12:00:47 +0100, Simon Riggs wrote: > On 12 May 2014 08:15, Andres Freund <andres@2ndquadrant.com> wrote: > > >> But I concur that in practice, if you're dealing with 16TB tables, it's time > >> to partition. > > > > Well, we need to improve our partitioning for that to be viable for all > > relations. Not having usable foreign and unique keys makes it a pita in > > some cases. > > As discussed, declarative partitioning is on the roadmap for this next > release, so I would say lets just document that tablesizes above 16TB > don't report correctly and move on. I doubt we'll fix all the snags - like foreign keys, unique keys, etc - that partitioning has in this release... Introducing a blocknumber type seems easy and mechanical enough. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: