On Fri, 2009-06-05 at 15:50 -0400, Bruce Momjian wrote:
> Brad Nicholson wrote:
> > I've been kicking the tires on this a bit, and I've found an issue when
> > dealing with contrib/ (specifically dblink, although I haven't looked
> > around anymore).
> >
uld be nice. Even better would be a sanity check
added to prevent this.
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
> significant loss of usability going from 8.2 to 8.3, in the minds of
> many people.
I put my hand up as one of those people.
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql
ossible but normally it only happens
> line-by-line at worst. This must have something to do with the
> buffering behavior on stderr. Perhaps the difference is caused
> by a difference in where the postmaster's stderr originally pointed
> --- was this postmaster started in a differe
Tom Lane wrote:
> Brad Nicholson <[EMAIL PROTECTED]> writes:
>> It may or may not be the same issue, but for what it's worth, we've seen
>> the same sl_log_1 corruption on AIX 5.1 and 5.3
>
> Hm, on what filesystem, and what PG version(s)?
>
> I
Brad Nicholson wrote:
> Tom Lane wrote:
>> Marc Munro <[EMAIL PROTECTED]> writes:
>>> I'll get back to you with kernel build information tomorrow. We'll also
>>> try to talk to some kernel hackers about this.
>> Some googling turned up recent discu
Linux NFS code:
>
> http://threebit.net/mail-archive/linux-kernel/msg05313.html
> http://lkml.org/lkml/2006/3/1/381
>
> I don't know the kernel nearly well enough to guess if these are related
> ...
It may or may not be the same issue, but for what it's worth, we
04a30 in PostgresMain (argc=4, argv=0x202706b0,
username=0x20270620 "slony") at postgres.c:2877
#16 0x10036f70 in BackendFork (port=0x202a5c28) at postmaster.c:2564
#17 0x10036908 in BackendStartup (port=0x202a5c28) at postmaster.c:2207
#18 0x10034bb0 in ServerLoop () at postmaster.c:11
Oleg Bartunov wrote:
Joshua,
does RT has full support of PostgreSQL ?
It support's Postgres, but it uses a dynamic query builder that is
pretty brain dead. It only implements features that are cross DB
compatible. It comes up with some pretty ugly queries.
--
Brad Nicholson 416-673
./configure --enable-debug --with-perl
==
All 96 tests passed.
==
uname -a
Linux richard 2.6.5-7.111.19-smp #1 SMP Fri Dec 10 15:10:58 UTC 2004
x86_64 x86_64 x86_64 GNU/Linux
--
Brad Nicholson
Database Administrator, Afilias Canada Corp
AIX 5.1
I applied Bruce's patch, configured with --enable-thread-safety and
everything went smoothly.
==
All 96 tests passed.
==
Brad.
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to
Bruce Momjian wrote:
Brad Nicholson wrote:
OK, I assume you used --enable-thread-safety in configure.
Correct.
This should
have added some PTHREAD link flags to your libpq build, and those
settings should have followed the libpq library into your pg_ctl link
line.
Would you look
Bruce Momjian wrote:
Brad Nicholson wrote:
I tried compliling v8 beta 5 (grabbed from cvs on Friday) on AIX 5.1.
It fails during the make
make[4]: Entering directory
`/opt/OXRS/Sources/pgsql-HEAD/src/interfaces/libpq'
make[4]: Nothing to be done for `all'.
make[4]: Leaving direct
I tried compliling v8 beta 5 (grabbed from cvs on Friday) on AIX 5.1.
It fails during the make
make[4]: Entering directory
`/opt/OXRS/Sources/pgsql-HEAD/src/interfaces/libpq'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/opt/OXRS/Sources/pgsql-HEAD/src/interfaces/libpq'
m
Tried to install this on AIX 5.1, no luck (compiles fine without
--enable-thread-safety though) .
AIX 5.1
gcc 3.3.2
./configure --prefix=/opt/dbs/pgsql800b3-AIX51-2004-09-30
--with-includes=/opt/dbs/readline-5-AIX51-2004-09-29/include:/opt/dbs/zlib-121-AIX51-2004-09-29/include:/opt/dbs/gdb-621-
15 matches
Mail list logo
