pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Eric Jain <Eric.Jain@isb-sib.ch>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: Fixed width rows faster?
Date: Mon, 8 Mar 2004 10:39:59 +0100
Message-ID: <004101c404f1$537989c0$c300000a@caliente> (raw)
References: <E9C9F3C2-6EA9-11D8-A89E-000D9366F0C4@torgo.978.org>
	<404889A6.7@potentialtech.com>
	<200403051528.55578.josh@agliodbs.com>
	<004501c4037d$63e27f80$c300000a@caliente>
	<18296.1078606346@sss.pgh.pa.us>

> This is bogus reasoning.  The limit on index entry length will not
> change when you rebuild the index.

What I meant by 'rebuilding' was not issuing a REINDEX command, but
creating a new index after having dropped the index and inserted
whatever records. Building indexes can be slow, and I'd rather not have
the operation fail after several hours because record #98556761 is
deemed to be too long for indexing...

While we are busy complaining, it's a pity Postgres doesn't allow us to
disable and later recreate all indexes on a table using a single command
;-)




view thread (23+ messages)

Message-ID: <004101c404f1$537989c0$c300000a@caliente>
Permalink:  ../004101c404f1$537989c0$c300000a@caliente/
Also on:    postgresql.org/message-id/004101c404f1$537989c0$c300000a@caliente

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: Eric.Jain@isb-sib.ch, tgl@sss.pgh.pa.us
  Subject: Re: Fixed width rows faster?
  In-Reply-To: <004101c404f1$537989c0$c300000a@caliente>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox