"Qingqing Zhou" <[EMAIL PROTECTED]> writes:
> On a separate matter, top level "make PROFILE=-pg" does not work on SunOS,
> because of -fPIC conflicts with -pg. Backend level is ok. Shall we do
> something or let it be?
This has always been true on some platforms; nothing we can do about it.
My h
"Tom Lane" <[EMAIL PROTECTED]> wrote
>
> Works fine for me in Fedora Core 4. Something broken about your
> platform, is my guess ...
>
You may want to talk to our system admin :-) ... but it doesn't look like
caused by some strange environment ...
/h/164/zhouqq/pginstall/bin#uname -a
Linux eon.
Roddi Walker wrote:
> This BOM header is legal - see http://www.unicode.org/faq/utf_bom.html#BOM -
> but probably used only on Windows.
Well, that FAQ says that the marker could be prohibited under some
higher-level protocols, so I guess this is one of them.
--
Alvaro Herrera ht
Qingqing Zhou <[EMAIL PROTECTED]> writes:
> I do "make PROFILE=-pg" on top level, seems everything is ok. When
> postmaster starts up, gmon.out is generated. But when I do use psql to
> connect to postmaster, a repeatable segment fault happens no matter what
> command you do in psql:
Works fine fo
I do "make PROFILE=-pg" on top level, seems everything is ok. When
postmaster starts up, gmon.out is generated. But when I do use psql to
connect to postmaster, a repeatable segment fault happens no matter what
command you do in psql:
sh-2.05a$ psql test
Welcome to psql 8.1RC1, the PostgreSQL int
"Michael Enke" <[EMAIL PROTECTED]> writes:
> A 'C' function, which uses the SPI_fnumber,
> which was compiled on 7.4.8 crashes the 8.0.3 server
> with a SIGSEGV.
> The same source code, compiled on 8.0.3
> makes no trouble.
This is not a bug, sorry. We have never promised compatibility of
dynamic
Brandon Black <[EMAIL PROTECTED]> writes:
> ERROR: too many trigger records found for relation "important_table"
> But then it all goes back to normal until it happens again the next
> morning. Remember, "important_table" has no triggers that I know of.
... except all the foreign-key triggers.
The following bug has been logged online:
Bug reference: 2012
Logged by: Michael Enke
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Linux SuSE 10
Description:SPI_fnumber sigsegv when compiled with 7.4.8
Details:
A 'C' function, which u
The following bug has been logged online:
Bug reference: 2011
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1RC1
Operating system: Linux ckrjmax 2.6.12-9-386
Description:warning during link of plperl
Details:
gcc -O2 -Wall -Wmissing-prototypes -
>Subject: Re: concurrent drop table with fkeys corrupt pg_trigger
>Date: Thu, 26 May 2005 09:47:25 +0800"
>Qingqing Zhou" writes
>> If we concurrently perform drop/create table (with foreign keys) commands
>> several times, we could corrupt the pg_trigger system table.
>>
>
>Anybody reproduced it?
10 matches
Mail list logo
