From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
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 14:47:49 |
Message-ID: | Pine.LNX.4.30.0107101644260.677-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Martijn van Oosterhout writes:
> Well, getting closer. Maybe I should start version numbering the patches?
For one thing, you might want to post them to pgsql-patches instead. And
you should start generating the patches against the 7.2devel sources
because I already suspect yours generating conflicts.
> * Updates to the documentation as well as comments within the code. If you
> see a spot I missed, let me know.
FYI, it's called partial "indexes".
> * Make it pg_dump-able. I've tried to extract the expression out the of
> system tables by using stringToNode and deparse_expression but it doesn't
> seem to work. I keep getting the error: "get_names_for_var: bogus
> varlevelsup 0". Anyone know what's going on? See attachment <<expr.c>>.
It might be an option to store the unparsed condition in the system
catalogs, similar to what is done with the default values (see
pg_attrdef).
--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter
From | Date | Subject | |
---|---|---|---|
Next Message | Fernando Schapachnik | 2001-07-10 14:54:45 | TCL and encoding |
Previous Message | Peter Eisentraut | 2001-07-10 14:37:11 | Re: problem in compilation. |