Re: [GENERAL] index organized tables use case

On Dec 12, 2007 9:16 PM, Robert Treat <[EMAIL PROTECTED]> wrote: > On Wednesday 12 December 2007 10:53, Thomas Kellerer wrote: > > At least for Oracle it's not mainly the order that improves the > > performance, but the fact that all the data is kept in the index, so > > Oracle does not need to go

Re: [GENERAL] index organized tables use case

On Wednesday 12 December 2007 10:53, Thomas Kellerer wrote: > Richard Huxton, 12.12.2007 16:12: > > Hmm - I'm not sure it does benefit that much. I mean, if you're going to > > be accessing XXXA, then XXXB, XXXC etc. in order then it clearly helps > > to have the table with the same order as your p

Re: [GENERAL] index organized tables use case

Richard Huxton, 12.12.2007 16:12: Hmm - I'm not sure it does benefit that much. I mean, if you're going to be accessing XXXA, then XXXB, XXXC etc. in order then it clearly helps to have the table with the same order as your primary key. Otherwise, I'd be doubtful you'd see that much benefit.

Re: [GENERAL] index organized tables use case

Enrico Sirola wrote: The application code usually performs selection queries like select tag, value from test where code='XXX'; also, deletions are like delete from test where code='XXX'; and insertions follow the same pattern (all the data for a code is inserted using a loop in a single tran

Re: [GENERAL] index organized tables use case

On 12/12/07, Enrico Sirola <[EMAIL PROTECTED]> wrote: > Hello Isak, > > Isak Hansen ha scritto: > > > Have a look at the cluster operation; > > . > > > > AFAIK it does lock & duplicate the whole table during reordering, > > which may or ma

[GENERAL] index organized tables use case

Hello, I'm thinking about migrating from another DBMS to postgresql. I have an almost working proof of concept, but still have some doubts about the following use case. I have a table like the following CREATE TABLE test ( code character varying(32) NOT NULL, tag integer NOT NULL, value dou