On Tue, Jul 19, 2005 at 06:06:00PM -0500, Jim C. Nasby wrote:
> [EMAIL
> PROTECTED]:00]~/buildfarm/HEAD/pgsqlkeep.1121809875/src/pl/plpython:41%otool
> -L libplpython.0.0.so
> libplpython.0.0.so:
> /System/Library/Frameworks/Python.framework/Versions/2.3/Python
> (compatibility version
On Tue, 2005-07-19 at 17:50 -0500, Jim C. Nasby wrote:
> On Tue, Jul 19, 2005 at 10:23:49PM +0100, Simon Riggs wrote:
> > Inheritance queries would continue to act as they do now, where an
> > excluded table is *not* shown; this is to allow for sensible size
> > EXPLAINs when we have 100s of child
On Tue, Jul 19, 2005 at 04:51:03PM -0500, Jim C. Nasby wrote:
> > Can you search the system for all files named libpython* and post
> > what you find?
>
> [EMAIL PROTECTED]:42]~:11%locate libpython
> /Applications/NeoOfficeJ.app/Contents/MacOS/libpython.dylib
> /Applications/NeoOfficeJ.app/Content
On Tue, Jul 19, 2005 at 10:23:49PM +0100, Simon Riggs wrote:
> Inheritance queries would continue to act as they do now, where an
> excluded table is *not* shown; this is to allow for sensible size
> EXPLAINs when we have 100s of child tables.
Since it's also possible to do partitioning with UNION
On Tue, Jul 19, 2005 at 02:42:07PM -0600, Michael Fuhr wrote:
> On Tue, Jul 19, 2005 at 03:11:35PM -0500, Jim C. Nasby wrote:
> > On Tue, Jul 19, 2005 at 01:54:00PM -0600, Michael Fuhr wrote:
> > > Does this machine have ldd or the equivalent? If so, can you compare
> > > "ldd /path/to/python" and
So far, the CE patch covers only inherited child tables and is only
effective when enable_constraint_exclusion is true.
There have been various requests for this to work with UNION ALL views
and also with normal queries.
Since we have a GUC that can turn this behaviour off, and is off by
default,
Jim C. Nasby wrote:
And the buildfarm script seems
to clean everything up even in the pgsqlkeep directories; or at least I
couldn't find a plpython.so laying around.
Nothing should be removed. If you are using the experimental code I
recently gave you all bets are off, but under normal c
On Tue, Jul 19, 2005 at 03:11:35PM -0500, Jim C. Nasby wrote:
> On Tue, Jul 19, 2005 at 01:54:00PM -0600, Michael Fuhr wrote:
> > Does this machine have ldd or the equivalent? If so, can you compare
> > "ldd /path/to/python" and "ldd /path/to/plpython.so"?
>
> Oddly, no, it doesn't seem to have l
On 7/19/05, Jim C. Nasby <[EMAIL PROTECTED]> wrote:
> The email below about FreeBSD's involvement in Google's Summer of Code
> got me thinking; would there be value in trying to attract college
> students to working on either PostgreSQL development, or using
> PostgreSQL in projects? Even though we
On Tue, Jul 19, 2005 at 01:54:00PM -0600, Michael Fuhr wrote:
> On Tue, Jul 19, 2005 at 02:48:52PM -0400, Tom Lane wrote:
> > "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > > I don't think it's a version issue; cuckoo is at 2.4, platypus used to
> > > be at 2.3 but I upgraded it to 2.4 to see if th
Josh Berkus writes:
> So, now that we know what the performance bottleneck is, how do we fix it?
Josh, I see that all of those runs seem to be using wal_buffers = 8.
Have you tried materially increasing wal_buffers (say to 100 or 1000)
and/or experimenting with different wal_sync_method options s
And 7.3 is also failing, with a different error:
ccache gcc -traditional-cpp -g -O2 -fno-strict-aliasing -g -Wall
-Wmissing-prototypes -Wmissing-declarations -I../../../../src/include
-I/opt/local/include -c -o printtup.o printtup.c
In file included from /usr/include/machine/param.h:30,
On Tue, Jul 19, 2005 at 03:53:26PM -0400, Andrew Dunstan wrote:
> Do you have any other libpython*.so files on your system?
[EMAIL PROTECTED]:56]~:2>locate libpython
/usr/local/lib/compat/pkg/libpython2.3.so.1
/usr/local/lib/libpython2.4.so
/usr/local/lib/libpython2.4.so.1
/usr/local/lib/python2.4/
Tom Lane wrote:
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
On Tue, Jul 19, 2005 at 03:11:31PM -0400, Tom Lane wrote:
None of those patches are necessary; if they were, we'd be seeing the
failures at the build stage, not at runtime.
Anyone have any ideas on why octopus is
On Tue, Jul 19, 2005 at 03:47:48PM -0400, Tom Lane wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > On Tue, Jul 19, 2005 at 03:11:31PM -0400, Tom Lane wrote:
> >> None of those patches are necessary; if they were, we'd be seeing the
> >> failures at the build stage, not at runtime.
>
> > An
On Tue, Jul 19, 2005 at 02:48:52PM -0400, Tom Lane wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > I don't think it's a version issue; cuckoo is at 2.4, platypus used to
> > be at 2.3 but I upgraded it to 2.4 to see if that was the issue, but
> > platypus kept working.
>
> Hmm ... if it's
Jim C. Nasby wrote:
On Tue, Jul 19, 2005 at 03:11:31PM -0400, Tom Lane wrote:
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
http://archives.postgresql.org/pgsql-bugs/2005-07/msg00096.php describes
what I think is causing octopus to fail. What's also interesting is
these patches from the
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> On Tue, Jul 19, 2005 at 03:11:31PM -0400, Tom Lane wrote:
>> None of those patches are necessary; if they were, we'd be seeing the
>> failures at the build stage, not at runtime.
> Anyone have any ideas on why octopus is failing then?
Well, the origina
(trimming cc list...)
On Tue, Jul 19, 2005 at 02:25:38PM -0500, Jim C. Nasby wrote:
> OK, I'll tweak cuckoo's config accordingly then.
And now it's failing on make, at least for 7.2...
ccache gcc -O3 -pipe -traditional-cpp -g -O2 -g -Wall
-Wmissing-prototypes -Wmissing-declarations -I. -I../../.
On Tue, Jul 19, 2005 at 03:17:49PM -0400, Andrew Dunstan wrote:
>
>
> Jim C. Nasby wrote:
>
> >Then I guess the question is... is it more valuable to have a working
> >buildfarm environment for 7.2 and 7.3, or is the obnoxious failure
> >better to spur someone into looking at it? :) Should this
On Tue, Jul 19, 2005 at 03:11:31PM -0400, Tom Lane wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > http://archives.postgresql.org/pgsql-bugs/2005-07/msg00096.php describes
> > what I think is causing octopus to fail. What's also interesting is
> > these patches from the FreeBSD port:
>
> N
Jim C. Nasby wrote:
Then I guess the question is... is it more valuable to have a working
buildfarm environment for 7.2 and 7.3, or is the obnoxious failure
better to spur someone into looking at it? :) Should this maybe be made
a TODO and I'll adjust my config until someone tackles the TODO?
The email below about FreeBSD's involvement in Google's Summer of Code
got me thinking; would there be value in trying to attract college
students to working on either PostgreSQL development, or using
PostgreSQL in projects? Even though we missed getting in on the summer
of code this year, ISTM tha
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> http://archives.postgresql.org/pgsql-bugs/2005-07/msg00096.php describes
> what I think is causing octopus to fail. What's also interesting is
> these patches from the FreeBSD port:
None of those patches are necessary; if they were, we'd be seeing the
f
http://archives.postgresql.org/pgsql-bugs/2005-07/msg00096.php describes
what I think is causing octopus to fail. What's also interesting is
these patches from the FreeBSD port:
[EMAIL PROTECTED]:48]/usr/ports/databases/postgresql80-server/files:37>cat
patch-plpython-Makefile patch-src-makefiles-
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> On Tue, Jul 19, 2005 at 10:03:39AM -0400, Tom Lane wrote:
>> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
>>> Attached is a plpython_error_1.out file that will fix cuckoo.
>>
>> What is the reason for the difference in the error message spelling
>> in the
Hi Tom,
good to hear from you. It was my miss-understanding of what the code was
doing, not the issue with the compiler :>
At 03:22 PM 7/19/2005, Tom Lane wrote:
Chris Bowlby <[EMAIL PROTECTED]> writes:
> I understand the concept of the code, to append binary values to a string
> buffer (cha
On Tue, Jul 19, 2005 at 02:29:08PM -0400, Tom Lane wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > On Sat, Jul 16, 2005 at 11:17:29PM -0400, Tom Lane wrote:
> >> cuckoo [7.3, 7.2]: --enable-nls without OS support
> >>
> >> This looks like pilot error; but the later branches don't fail on t
Ahh, so it's not attempting to turn it into an "acsii" string, just storing
raw binary data... Ok that makes sense now, thanks for the help.
At 02:54 PM 7/19/2005, Korry wrote:
If I understand the code right, your trying to pass in to
appendBinaryStringInfo an "address" or reference to the n8
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> On Sat, Jul 16, 2005 at 11:17:29PM -0400, Tom Lane wrote:
>> cuckoo [7.3, 7.2]: --enable-nls without OS support
>>
>> This looks like pilot error; but the later branches don't fail on this
>> machine, so did we change something in this area?
> Should I
Chris Bowlby <[EMAIL PROTECTED]> writes:
> I understand the concept of the code, to append binary values to a string
> buffer (char *), but, under my compiler on FreeBSD 5.4.x (gcc (GCC) 3.4.2
> [FreeBSD] 20040728) I see a few issues that have cropped up.
You've got a broken compiler then, becau
On Jul 19 2005, Tom Lane wrote:
Larry Rosenman writes:
> Looks like it's time for an update to the config.guess/config.sub
> scripts.
Didn't we just do that?
2005-07-01 14:17 petere
* configure, configure.in, config/config.guess, config/config.sub,
config/install-sh, confi
On Sat, Jul 16, 2005 at 11:17:29PM -0400, Tom Lane wrote:
> cuckoo [7.3, 7.2]: --enable-nls without OS support
>
> This looks like pilot error; but the later branches don't fail on this
> machine, so did we change something in this area?
Should I just stop using nls on 7.2 and 7.3 or does someone
Larry Rosenman writes:
> Looks like it's time for an update to the config.guess/config.sub scripts.
Didn't we just do that?
2005-07-01 14:17 petere
* configure, configure.in, config/config.guess, config/config.sub,
config/install-sh, config/mkinstalldirs,
src/include/pg
On Jul 19 2005, Peter Eisentraut wrote:
Larry Rosenman wrote:
> Do I need to generate a patch, or can we just get them updated in
> HEAD?
They were updated two weeks ago and there weren't any SCO-related
changes since then. If you have patches, please submit them to
<[EMAIL PROTECTED]> first
Larry Rosenman wrote:
> Do I need to generate a patch, or can we just get them updated in
> HEAD?
They were updated two weeks ago and there weren't any SCO-related
changes since then. If you have patches, please submit them to
<[EMAIL PROTECTED]> first.
--
Peter Eisentraut
http://developer.po
If I understand the code right, your trying to pass in to
appendBinaryStringInfo an "address" or reference to the n8, n16, or n32
variables and cast them so that a char * pointer can access that address
space. Through some testing that I've been doing (outputting the values in
the appendB
Hi All,
I've been doing a code audit (review) for my own personal use of the
7.4.x series code base and have come across something that I'd like to get
more details on, if it is possible to do so.
I've been going over the communications section and am curious how this
segment of code is ac
Looks like it's time for an update to the config.guess/config.sub scripts.
SCO (don't yell, I'm just the messenger), released OpenServer 6, and needs
updated versions to compile.
Do I need to generate a patch, or can we just get them updated in HEAD?
LER
--
Larry Rosenman
I'm switching the aftermath of this thread -- http://archives.postgresql.org/pgsql-general/2005-07/msg00501.php -- to -hackers since it raised issues of potential concern to developers.At various points in the thread, Tom Lane said the following:"I have an old note to myself that persistent write e
On Mon, Jul 18, 2005 at 03:01:31PM -0400, Tom Lane wrote:
> Andrew - Supernews <[EMAIL PROTECTED]> writes:
> >>> "WHERE spcname NOT LIKE E'pg\\_%'");
>
> > It's not even correct as it stands - if you want to match a literal _
> > using LIKE then you would need E'pg_%' there.
>
> Good point!
>
41 matches
Mail list logo
