| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
| Subject: | Re: generic reloptions improvement |
| Date: | 2008-12-24 10:38:26 |
| Message-ID: | 200812241238.28186.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Monday 22 December 2008 18:24:53 Alvaro Herrera wrote:
> > Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> > > Here's a patch for improving the general reloptions mechanism. What
> > > this patch does is add a table-based option parser. This allows adding
> > > new options very easily, and stops the business of having to pass the
> > > minimum and default fillfactor each time you want the reloptions
> > > processed.
> Here's the next version, which also fixes some particularly embarrasing
> bugs.
I'm not sure how important this is, but if you are enumerating the access
methods (RELOPT_KIND_BTREE, etc.), how will this work with user-defined
access methods?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-12-24 10:53:00 | Re: Synchronous replication, reading WAL for sending |
| Previous Message | Simon Riggs | 2008-12-24 10:26:42 | Re: Archiving control (a part of synch rep patches) |