Re: [BUGS] BUG #2401: spinlocks not available on amd64

2009-06-24 Thread Theo Schlossnagle
code, the CAS stuff should just work. On Jun 24, 2009, at 8:27 AM, Gregory Stark wrote: Theo Schlossnagle wrote: Tom Lane wrote: There is no reason for the i386 or AMD64 code to be different from what's already tested on Linux --- the hardware's the same and the OS surely

Re: [BUGS] plperl.c patch to correctly support bytea inputs and output to functions and triggers.

2007-04-30 Thread Theo Schlossnagle
On Apr 30, 2007, at 11:32 AM, Tom Lane wrote: Theo Schlossnagle <[EMAIL PROTECTED]> writes: As a note, the return from the function is a bytea, so no decoding is done. If I return a string with a \0 in it, then it will be clipped short. If I return a string with a "\\000" i

Re: [BUGS] plperl.c patch to correctly support bytea inputs and output to functions and triggers.

2007-04-30 Thread Theo Schlossnagle
Tom Lane wrote: Theo Schlossnagle <[EMAIL PROTECTED]> writes: If I return a bytes from perl that looks like: "hello\0there", postgres sees a 5 byte string "hello". You have failed to pay any attention to the escaping rules for bytea if you do that. As a note, th

Re: [BUGS] plperl.c patch to correctly support bytea inputs and output to functions and triggers.

2007-04-29 Thread Theo Schlossnagle
On Apr 28, 2007, at 1:26 PM, Tom Lane wrote: Theo Schlossnagle <[EMAIL PROTECTED]> writes: I've found a bug with the way plperl/plperlu handles bytea types. It fails to correctly handle bytea binary inputs and outputs. Define "correctly". The proposed patch seems to b

[BUGS] plperl.c patch to correctly support bytea inputs and output to functions and triggers.

2007-04-28 Thread Theo Schlossnagle
| octet_length -+-- 2 |2 (1 row) pltest=# select pl_produce_bytea(), octet_length(pl_produce_bytea()); pl_produce_bytea | octet_length -+-- \000\000\000\000\000\000see me? | 13 (1 ro

Re: [BUGS] BUG #2401: spinlocks not available on amd64

2006-04-21 Thread Theo Schlossnagle
e I was at it, I believe I reduced the complexity of code and offered (with pg_atomic_cas) an opportunity to ascertain _who_ holds the lock when you have spinlock contention. (as you could potentially cas the lock to the pg procpid instead of 1 at no additional cost). Best regards, Theo -

Re: [BUGS] BUG #2401: spinlocks not available on amd64

2006-04-21 Thread Theo Schlossnagle
On Apr 19, 2006, at 11:17 PM, Bruce Momjian wrote: Theo Schlossnagle wrote: The following bug has been logged online: Bug reference: 2401 Logged by: Theo Schlossnagle Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.3 Operating system: Solaris 10 Description

[BUGS] BUG #2401: spinlocks not available on amd64

2006-04-19 Thread Theo Schlossnagle
The following bug has been logged online: Bug reference: 2401 Logged by: Theo Schlossnagle Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.3 Operating system: Solaris 10 Description:spinlocks not available on amd64 Details: Compiling 8.1.3 on solaris 10

[BUGS] BUG #1917: autovaccuum crashes

2005-09-28 Thread Theo Schlossnagle
The following bug has been logged online: Bug reference: 1917 Logged by: Theo Schlossnagle Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1devel Operating system: CentOS 4.1 (Linux 2.6.12.3) Description:autovaccuum crashes Details: We're runni