"Phil Criley" <[EMAIL PROTECTED]> writes:
> We run FC5 on a server. PostgreSQL does not accept passwords when set to
> md5, I deleted version 8.1 and installed the latest, 8.2 from source. That's
> when I discovered that the install script in Fedora's RPM put postgreSQL in
> the /var/lib/pgsql but
On Mon, Apr 30, 2007 at 12:12:11PM -0400, Kenneth Downs wrote:
> Tom Lane wrote:
> >Kenneth Downs <[EMAIL PROTECTED]> writes:
> >
> >>Here is a test case to show that plperl functions are not re-entrant.
> >>
> >
> >I'm very bad in perl, but I think you need to declare all your variables
> >w
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" in it, I will get t
The following bug has been logged online:
Bug reference: 3258
Logged by: Phil Criley
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1 and 8.2
Operating system: Fedora Core 5
Description:Password fails, RPM installs in wrong directory
Details:
We run FC5 on a
Tom Lane wrote:
Kenneth Downs <[EMAIL PROTECTED]> writes:
Here is a test case to show that plperl functions are not re-entrant.
I'm very bad in perl, but I think you need to declare all your variables
with "my" to make them local instead of global.
regards, tom
Kenneth Downs <[EMAIL PROTECTED]> writes:
> Here is a test case to show that plperl functions are not re-entrant.
I'm very bad in perl, but I think you need to declare all your variables
with "my" to make them local instead of global.
regards, tom lane
---
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" in it, I will get the
> four-character string \000. There is
Here is a test case to show that plperl functions are not re-entrant.
Level_one: one row
Level_two: one row
Level_thr: one row
The idea is that an AFTER STATEMENT UPDATE trigger on Level_thr calls a
plperl routine. The plperl routine has a hardcoded 3-pass loop that
updates table Level_two.
Here is a test case to show that plperl functions are not re-entrant.
Level_one: one row
Level_two: one row
Level_thr: one row
The idea is that an AFTER STATEMENT UPDATE trigger on Level_thr calls a
plperl routine. The plperl routine has a hardcoded 3-pass loop that
updates table Level_two.
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, the return from the function is
On Tue, Feb 27, 2007 at 02:08:38PM -0500, Bruce Momjian wrote:
> Magnus Hagander wrote:
> > On Tue, Feb 27, 2007 at 09:06:17AM -0500, Phil Frost wrote:
> > > Hrm...I haven't used windows for a while now, but isn't there an
> > > option on all shortcuts to command-line programs to make the shell
11 matches
Mail list logo
