Neil Conway <[EMAIL PROTECTED]> writes:
> On Thu, 2007-07-05 at 16:32 -0400, Tom Lane wrote:
>> By and large we don't try to support nonstandard compilers on Linux.
> We support icc on Linux, at least to some degree (buildfarm members
> mongoose and dugong, for example).
Well, that's because (a)
On Thu, 2007-07-05 at 16:32 -0400, Tom Lane wrote:
> By and large we don't try to support nonstandard compilers on Linux.
We support icc on Linux, at least to some degree (buildfarm members
mongoose and dugong, for example). I don't see anything wrong with
supporting Sun Studio on Linux, if someon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jul 05, 2007 at 03:22:17PM -0500, Larry Rosenman wrote:
> try:
> DROP TABLE "MULTIPOLYGON";
>
> That should do it.
> (pardon the top post).
>
>
>
> --
> Larry Rosenman http://www.lerctr.org/~ler
> Phone: +1 512-248-2683
"Len Zaifman" <[EMAIL PROTECTED]> writes:
> The following error occuredbuilding Postgresql 8.2.4 on SLES 9 using SUN
> STUDIO 12 compilers
> sunstudio12/bin/cc -O -I../../../../src/include -D_GNU_SOURCE -c -o xlog.o
> xlog.c
> "../../../../src/include/storage/s_lock.h", line 810: #error: Postg
try:
DROP TABLE "MULTIPOLYGON";
That should do it.
(pardon the top post).
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683E-Mail: [EMAIL PROTECTED]
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
-Original Message-
From: [EMAI
The following error occuredbuilding Postgresql 8.2.4 on SLES 9 using SUN
STUDIO 12 compilers
sunstudio12/bin/cc -O -I../../../../src/include -D_GNU_SOURCE -c -o xlog.o
xlog.c
"../../../../src/include/storage/s_lock.h", line 810: #error: PostgreSQL does
not have native spinlock support on this
The following bug has been logged online:
Bug reference: 3429
Logged by: James White
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: debian etch amd64
Description:table named MULTIPOLYGON
Details:
I accidentally created a table name mult
Matt Taylor <[EMAIL PROTECTED]> writes:
> On Thu, 2007-07-05 at 00:13 -0400, Tom Lane wrote:
>> IIRC, "char" means "char(1)" by default, so I'm unconvinced that this
>> behavior is a bug.
> Since 'character' is not accepted as a valid type by spi_prepare, is
> this bug a duplicate of BUG #2917? M
On Thu, 2007-07-05 at 00:13 -0400, Tom Lane wrote:
> "Matt Taylor" <[EMAIL PROTECTED]> writes:
> > The spi_prepare and spi_exec_prepared doesn't seem to properly handle fixed
> > character types. Only the first character of a string is passed to the
> > database.
>
> IIRC, "char" means "char(1)
