enable_joinremoval
in [PgSql]
|
From: Simon Riggs on 29 Mar 2010 16:11 On Mon, 2010-03-29 at 15:55 -0400, Tom Lane wrote: > Simon Riggs <simon(a)2ndQuadrant.com> writes: > > On Mon, 2010-03-29 at 13:31 -0600, Alex Hunsaker wrote: > >> On Mon, Mar 29, 2010 at 12:17, Simon Riggs <simon(a)2ndquadrant.com> wrote: > >>> You're not addressing the original point. I have been asked how would > >>> users know which tables have been removed and whether there is a way of > >>> checking that. > >> > >> Uhh... they wont be in the explain output... Seems simple enough. > > > That is exactly what I replied, though nobody felt that was a great > > answer. > > Who complained about that exactly? It seems like a perfectly > appropriate answer to me. I'm relaying feedback from others not on this list. People expect me to do this. I shouldn't need to name them for us to accept the feedback, nor should there be doubt that I relay this accurately (why else would I raise the subject?!?). If it comes from me, I say so. -- Simon Riggs www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Simon Riggs on 29 Mar 2010 16:13 On Mon, 2010-03-29 at 13:54 -0600, Alex Hunsaker wrote: > whatever happened to those hooks to auto create/recommend indexes? You haven't published them yet?? -- Simon Riggs www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Tom Lane on 29 Mar 2010 16:17 Alex Hunsaker <badalex(a)gmail.com> writes: > It comes to mind you can probably do this with an plannerhook > (whatever happened to those hooks to auto create/recommend indexes?) Uh, we made some hooks to let someone build an *external* module that would do such a thing. Whether anybody got anywhere with it I dunno. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Jaime Casanova on 29 Mar 2010 17:56 On Mon, Mar 29, 2010 at 3:57 PM, Robert Haas <robertmhaas(a)gmail.com> wrote: > On Mon, Mar 29, 2010 at 3:55 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote: >> Simon Riggs <simon(a)2ndQuadrant.com> writes: >>> On Mon, 2010-03-29 at 13:31 -0600, Alex Hunsaker wrote: >>>> On Mon, Mar 29, 2010 at 12:17, Simon Riggs <simon(a)2ndquadrant.com> wrote: >>>>> You're not addressing the original point. I have been asked how would >>>>> users know which tables have been removed and whether there is a way of >>>>> checking that. >>>> >>>> Uhh... they wont be in the explain output...  Seems simple enough. >> >>> That is exactly what I replied, though nobody felt that was a great >>> answer. >> >> Who complained about that exactly?  It seems like a perfectly >> appropriate answer to me. > > Jaime Casanova. > i'm just finishing to read an 347 rows EXPLAIN ANALYZE, so yes i prefer a DEBUG message than to hunt missing rels -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL AsesorÃa y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
First
|
Prev
|
Pages: 1 2 3 4 5 6 Prev: Problems with variable cursorname in ecpg Next: Using HStore type in TSearch |