Alex Goncharov wrote:
> Kevin Grittner wrote:
>> The rows will all be in the table, but not visible to any other
>> transaction.
>
> How much data can I fit there while doing COPY? Not 1 TB?
As has already been said, why not? This is not some special
section of the table -- the data is writte
[about loadling large amounts of data]
Felipe Santos wrote:
> This might also help:
> http://www.postgresql.org/docs/9.1/static/populate.html
>
>
> Bulk load tables from text files in almost all RDMS are "log free" (Postgres'
> COPY is one of them).
>
> The reason is that the database doesn't
This might also help:
http://www.postgresql.org/docs/9.1/static/populate.html
Bulk load tables from text files in almost all RDMS are "log free"
(Postgres' COPY is one of them).
The reason is that the database doesn't need to waste resources by writing
the log because there's no risk of data loss
Alex Goncharov wrote:
> Thank you, Kevin -- this is helpful.
>
> But it still leaves questions for me.
>> Alex Goncharov wrote:
>
>>> The whole thing is aborted then, and the good 99 records are not
>>> making it into the target table.
>>
>> Right. This is one reason people often batch such co
