On Tue, 2008-11-18 at 17:38 +0100, [EMAIL PROTECTED] wrote:
I bet there is no 'critical' length - this is just another case of
index
scan vs. seqscan. The efficiency depends on the size of the table /
row,
amount of data in the table, variability of the column used in the IN
clause, etc.
On Wed, 2008-07-30 at 17:16 +0100, Matthew Wakeling wrote:
I believe this SQL snippet could cause data loss, because there is a
period during which writes can be made to the old table that will not
be
copied to the new table.
It could indeed cause data loss.
On a side note, I would be
On Wed, 2008-07-30 at 13:51 -0400, Tom Lane wrote:
Huh? Vacuum doesn't block writes.
regards, tom lane
Of course, you are correct. I was thinking of Vacuum full, which is
recommended for use when you're deleting the majority of rows in a
table.
On Mon, 2008-06-30 at 18:57 +0200, Franck Routier wrote:
Hi,
I have problems with my database becoming huge in size (around 150 GB
right now, and 2/3 for only three tables, each having around 30 millions
tuples. Space is spent mainly on indices.).
I have a lot of multi-column varchar
