From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | Postgresql General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: [PATCH] Partial indicies again |
Date: | 2001-07-10 13:56:38 |
Message-ID: | 28736.994773398@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> To actually be able to use ExecInsertIndexTuples, you need to create an
> EState, a ResultRelInfo and put each tuple in a TupleSlot for a while. Does
> it sound like I'm on the right track? That's quite a few changes.
Right. I'd recommend copy.c as a model.
> Isn't someone else playing with the vacuum code for 7.2 anyway (for
> background vacuums)? We'd better make sure we don't clash.
That would be me.
> Back to other issues. pg_dump now works for partial indicies, as long as the
> pg_get_expr function is defined. To make that an internal function I have
> add it to pg_proc.h and initdb again, right?
Right. I'd suggest sticking the source in ruleutils.c.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Philip Molter | 2001-07-10 14:06:07 | Re: Performance tuning for linux, 1GB RAM, dual CPU? |
Previous Message | Janning Vygen | 2001-07-10 13:21:37 | Re: Performance tuning for linux, 1GB RAM, dual CPU? |