pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alexander Priem <ap@cict.nl>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Indexing question
Date: Fri, 29 Aug 2003 17:13:52 +0200
Message-ID: <027701c36e40$2851aef0$b696a8c0@APR> (raw)
References: <012f01c36dfa$0f4a8760$b696a8c0@APR>
	<3F4EFAB6.7030104@klaster.net>
	<015f01c36e02$134fe960$b696a8c0@APR>
	<3F4F07CE.6090803@klaster.net>
	<018c01c36e09$4893e980$b696a8c0@APR>
	<3F4F1575.8090600@klaster.net>
	<01bf01c36e0d$18769280$b696a8c0@APR>
	<15992.1062165614@sss.pgh.pa.us>

Well, the intention is to hold every record that ever existed in the table.
Therefore, records do not get deleted, but they get a date in the
deleteddate field. This way, we can track what changes were made to the
table(s).

So if a record gets 'deleted', the field 'deleted' is set to today's date.
If a record gets 'updated', a new record is made containing the new data,
and the old record is marked as 'deleted'.

So the percentage of 'deleted' records will grow with time, if you
understand what I mean.



----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Alexander Priem" <ap@cict.nl>
Cc: "Tomasz Myrta" <jasiek@klaster.net>; <pgsql-performance@postgresql.org>
Sent: Friday, August 29, 2003 4:00 PM
Subject: Re: [PERFORM] Indexing question


> "Alexander Priem" <ap@cict.nl> writes:
> > Does anyone know whether it is bad practise to have two indexes on the
> > primary key of a table? (one 'primary key' index and one partial index)
>
> It's a little unusual, but if you get enough performance boost from it
> to justify the maintenance cost of the extra index, then I can't see
> anything wrong with it.
>
> The "if" is worth checking though.  I missed the start of this thread,
> but what percentage of your rows do you expect to have null deleteddate?
> Unless it's a pretty small percentage, I'm unconvinced that the extra
> indexes will be worth their cost.
>
> regards, tom lane




view thread (15+ messages)  latest in thread

Message-ID: <027701c36e40$2851aef0$b696a8c0@APR>
Permalink:  ../027701c36e40$2851aef0$b696a8c0@APR/
Also on:    postgresql.org/message-id/027701c36e40$2851aef0$b696a8c0@APR

 · 

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: ap@cict.nl, tgl@sss.pgh.pa.us
  Subject: Re: Indexing question
  In-Reply-To: <027701c36e40$2851aef0$b696a8c0@APR>

* 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