| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | ow <oneway_111(at)yahoo(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Max number of rows in a table |
| Date: | 2003-12-01 16:09:03 |
| Message-ID: | 20031201080822.D45949@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 1 Dec 2003, ow wrote:
> > --- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Actually you can only have 4 billion SQL commands per xid, because the
> > CommandId datatype is also just 32 bits. I've never heard of anyone
> > running into that limit, though.
> >
>
> Wouldn't the above put a limit on a number of records one could have in table?
> One have to use pg_dump/pg_restore to be able to upgrade between pgSql releases
> and/or to backup data. If one cannot backup data and/or upgrade between pg
> releases, then 4B records is the effective limit on the number of records in
> pgSql ... or am I missing something?
I'd expect copy to be a single command, no matter how many rows were
copied.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2003-12-01 16:15:47 | Re: Partitions implementation with views |
| Previous Message | ow | 2003-12-01 16:08:55 | Re: Max number of rows in a table |