Re: [HACKERS] Max number of rows in a table

ow [EMAIL PROTECTED] writes: --- Tom Lane [EMAIL PROTECTED] 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

Re: [HACKERS] Max number of rows in a table

--- Tom Lane [EMAIL PROTECTED] wrote: Wouldn't the above put a limit on a number of records one could have in table? No. If I understand correctly, a table that has 4B+ rows cannot be restored after the dump and that, in turn, may/will affect the ability to upgrade to new versions of

Re: [HACKERS] Max number of rows in a table

On Mon, 1 Dec 2003, ow wrote: --- Tom Lane [EMAIL PROTECTED] 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

Re: [HACKERS] Max number of rows in a table

Stephan Szabo [EMAIL PROTECTED] writes: I'd expect copy to be a single command, no matter how many rows were copied. It might prevent you from using pg_dump --inserts ? -- greg ---(end of broadcast)--- TIP 5: Have you checked our extensive

Re: [HACKERS] Max number of rows in a table

ow [EMAIL PROTECTED] writes: If I understand correctly, a table that has 4B+ rows cannot be restored after the dump and that, in turn, may/will affect the ability to upgrade to new versions of pgSql. You don't understand correctly. regards, tom lane

Re: [HACKERS] Max number of rows in a table

--- Tom Lane [EMAIL PROTECTED] wrote: ow [EMAIL PROTECTED] writes: If I understand correctly, a table that has 4B+ rows cannot be restored after the dump and that, in turn, may/will affect the ability to upgrade to new versions of pgSql. You don't understand correctly. I see. Thanks

Re: [HACKERS] Max number of rows in a table

Clinging to sanity, [EMAIL PROTECTED] (ow) mumbled into her beard: --- Tom Lane [EMAIL PROTECTED] wrote: Wouldn't the above put a limit on a number of records one could have in table? No. If I understand correctly, a table that has 4B+ rows cannot be restored after the dump and that,

Re: [HACKERS] Max number of rows in a table

Greg Stark [EMAIL PROTECTED] writes: Stephan Szabo [EMAIL PROTECTED] writes: I'd expect copy to be a single command, no matter how many rows were copied. It might prevent you from using pg_dump --inserts ? Not even that, unless you *also* modified the dump output to wrap BEGIN/END around it.