Re: [BUGS] BUG #5652: Optimizer does wrong thing with partitioned tables
On Fri, Sep 10, 2010 at 11:34:16PM -0400, Mladen Gogala wrote: > Jeff Davis wrote: > >On Fri, 2010-09-10 at 16:53 -0400, Mladen Gogala wrote: > >>Jeff, that's the problem. Functions like "MAX" are rather ordinary > >>and frequently used. > > > >I agree that it could be improved. The best way to move such > >improvement forward is to advance the discussion on -hackers. Start > >with this thread here: > > > >http://archives.postgresql.org/pgsql-hackers/2009-07/msg01115.php > > > >and see if you have anything to add, or see if you can find related > >discussions. The main point is that -bugs is usually for short > >discussions about fixing defects that were just discovered, and > >-hackers is better for problems without an obvious solution, where > >discussion is required. > > > Thanks, I will do that. However, I cannot call myself a hacker, I > am but a mere beginner with Postgres. You're a hacker when you start hacking :) Cheers, David. -- David Fetter http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fet...@gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] 9.0 Bug: cannot build against python3.1, with two versions of python in the environment
I discussed this report with James Pye already, and he beleives it's a configure script bug which should be fixed before release. Anyone capable of taking it on? Original Message Subject:[TESTERS] Configure/Build 9.0 rc1 - cannot build against python3.1, with two versions of python in the environment Date: Sat, 11 Sep 2010 13:12:13 -0400 From: Lou Picciano To: pgsql-test...@postgresql.org *[TEST REPORT]* *[Release]:* 9.0 RC1 *[Test Type]:* Install (Build) *[Test]:* Configure/Build 9.0 rc1 - cannot build against python3.1, with two versions of python in the environment *[Platform]:* Solaris 10 Sparc E450 Quad *[Parameters]:* --with-python \ * --with-includes=/usr/local/include/python3.1:/usr/local/include:/usr/local/ssl/include \ --with-libraries=/usr/local/lib/python3.1:/usr/local/lib:/usr/local/ssl/lib \ CONFIGURE OUTPUT: - checking for python... /usr/bin/python checking Python configuration directory... /usr/lib/python2.4/config checking how to link an embedded Python application... -L/usr/lib -lpython2.4 -lresolv -lsocket -lnsl -lrt -ldl -lm configure: using CPPFLAGS= -I/usr/local/include/libxml2 -I/usr/local/include/python3.1 -I/usr/local/include -I/usr/local/ssl/include configure: using LDFLAGS= -L/usr/local/lib -L/usr/local/lib/python3.1 [Failure]:* Can't seem to definitively config PG to a specific version of python - v3.1, at /usr/local/bin/python3 *[Results]:* configure seems to pick up python 2.4 configuration, but apparently links to (desired) python 3.1 libs. # ldd plpython2.so libpython2.4.so.1.0 => /usr/lib/libpython2.4.so.1.0 *[Comments]:* Tried first to see if configure picks up the PYTHONPATH env variable to find python's configuration. No joy. Using this variable might be a reasonable approach for configure? -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] issue about information_schema REFERENTIAL_CONSTRAINTS
On Tue, Aug 31, 2010 at 10:46 AM, Tom Lane wrote: > We are not going to try to enforce uniqueness. This has been debated > before, and most people like the current behavior just fine, or at least > better than the alternatives. Really? I thought the issue was that no one had figured out how to do it, or that no one had written the patch, not that anyone thought the current behavior was particularly desirable. What happens if you say ALTER TABLE .. DROP CONSTRAINT or COMMENT ON CONSTRAINT? You just pick one at random? That's really what most people want? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] issue about information_schema REFERENTIAL_CONSTRAINTS
Robert Haas writes: > On Tue, Aug 31, 2010 at 10:46 AM, Tom Lane wrote: >> We are not going to try to enforce uniqueness. This has been debated >> before, and most people like the current behavior just fine, or at least >> better than the alternatives. > Really? I thought the issue was that no one had figured out how to do > it, or that no one had written the patch, not that anyone thought the > current behavior was particularly desirable. What happens if you say > ALTER TABLE .. DROP CONSTRAINT or COMMENT ON CONSTRAINT? You just > pick one at random? No, because those syntaxes constrain the choice to one single constraint. Perhaps if the SQL committee had designed 'em, there'd be an issue; but they are Postgres-isms. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] 9.0 Bug: cannot build against python3.1, with two versions of python in the environment
Josh Berkus writes: > I discussed this report with James Pye already, and he beleives it's a > configure script bug which should be fixed before release. Anyone > capable of taking it on? AFAICS, user has failed to ensure that only one Python version is visible in his environment. Please show cause why this isn't user error. > checking for python... /usr/bin/python > checking Python configuration directory... /usr/lib/python2.4/config > checking how to link an embedded Python application... -L/usr/lib > -lpython2.4 -lresolv -lsocket -lnsl -lrt -ldl -lm > configure: using CPPFLAGS= -I/usr/local/include/libxml2 > -I/usr/local/include/python3.1 -I/usr/local/include -I/usr/local/ssl/include > configure: using LDFLAGS= -L/usr/local/lib -L/usr/local/lib/python3.1 In particular, how'd those 3.1 references get in there when the python version in $PATH is 2.4? It's for damn sure we didn't introduce those. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
