Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Using multi-row technique with COPY
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Simon Riggs <simon(at)2ndquadrant(dot)com>
- Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: Using multi-row technique with COPY
- Date: Wed, 30 Nov 2005 02:10:58 -0500
- Message-id: <14048(dot)1133334658(at)sss(dot)pgh(dot)pa(dot)us>
Simon Riggs <simon(at)2ndquadrant(dot)com> writes: > [...context omitted...] > We would need to flush all the blocks in the table out of cache at > commit time, for that table only. This seems striking close to the Old Concept of temp tables, which we got rid of for good-and-sufficient reasons. You might want to spend some time reviewing the archives before proposing that we reintroduce it. regards, tom lane
- References:
- Re: Using multi-row technique with COPY
- From: Bruce Momjian
- Re: Using multi-row technique with COPY
- From: Simon Riggs
- Re: Using multi-row technique with COPY
- Prev by Date: Re: slow IN() clause for many cases
- Next by Date: Re: BIN()
- Previous by thread: Re: Using multi-row technique with COPY
- Next by thread: Re: Using multi-row technique with COPY
- Indexes: