| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Hans-Juergen Schoenig -- PostgreSQL <postgres(at)cybertec(dot)at> |
| Cc: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] contrib/plantuner - enable PostgreSQL planner hints |
| Date: | 2009-10-13 07:10:48 |
| Message-ID: | dcc563d10910130010h399ae98bl6ef336daa203c47c@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Mon, Oct 12, 2009 at 9:20 AM, Hans-Juergen Schoenig -- PostgreSQL
<postgres(at)cybertec(dot)at> wrote:
> if there was a vote whether this should be in contrib or in core: +999 from
> me ...
Well, contrib is a good place to start. It sets a clearly defined
ownership / maintenance person, and if the core of pgsql changes,
instead of the core hackers having to make this code happy, that job
then falls to the original contributor or whoever is willing to keep
it fed and working.
I think I'm gonna grab a copy and play with it, it sure could help in
the cases where the query planner just can't make the right decision
(correlation of indexes etc) Thanks to Oleg for this a bunch.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andre Brandt | 2009-10-13 10:40:37 | tar error while running basebackup |
| Previous Message | gerhard.lutz | 2009-10-13 07:07:48 | "Large object (lo)" and PostgreSQL 8.4 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-10-13 08:18:14 | Re: transaction_isolation vs. default_transaction_isolation |
| Previous Message | Jeff Davis | 2009-10-13 06:31:50 | missing entry in GucSource_Names |