"" <[EMAIL PROTECTED]> writes:
> PostgreSQL version: 8.2.0
> Operating system: Red Hat Enterprise Linux ES release 4
> Description:server crashes when trying to catch exception in
> function
I can't reproduce this using 8.2 branch tip. I suspect it is at bottom
the same problem as bug #
The following bug has been logged online:
Bug reference: 2946
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.0
Operating system: Red Hat Enterprise Linux ES release 4
Description:server crashes when trying to catch exception in
function
Details:
Hi,
Good news! We've succesfully installed Postgres on Windows Embedded.
The trick was to include a Null Device Driver to the image.
Thanks for your help!
Regards,
Maarten
-Oorspronkelijk bericht-
Van: Magnus Hagander [mailto:[EMAIL PROTECTED]
Verzonden: maandag 29 januari 2007 13:00
A
Sergiy Vyshnevetskiy <[EMAIL PROTECTED]> writes:
> Not at all. What's "broken" is the idea of variable as a simple piece of
> memory. It is correct for base types, but not for domains - they may have
> non-empty constructors (in C++ terminology).
That may be, but I'm unwilling to pay the overhea
On Wed, 31 Jan 2007, Tom Lane wrote:
Sergiy Vyshnevetskiy <[EMAIL PROTECTED]> writes:
This should fix the problem.
No, not at all. Consider if you'd written a domain CHECK constraint
that rejects nulls, instead of the easy case.
I've forgotten that.
What we'd really have to do here is see
Sergiy Vyshnevetskiy <[EMAIL PROTECTED]> writes:
> This should fix the problem.
No, not at all. Consider if you'd written a domain CHECK constraint
that rejects nulls, instead of the easy case. What we'd really have
to do here is see if domain_in() will accept a NULL.
I'm starting to get the fe
This should fix the problem.
--- src/pl/plpgsql/src/pl_comp.c.orig Wed Oct 4 03:30:13 2006
+++ src/pl/plpgsql/src/pl_comp.c Wed Jan 31 19:47:56 2007
@@ -1471,6 +1471,7 @@
var->value = 0;
var->isnull = true;
var->freeval = false;
+var->notnull = dtype->typnotnull;
plpgsql
The following bug has been logged online:
Bug reference: 2948
Logged by: Sergiy Vyshnevetskiy
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.1
Operating system: FreeBSD-6 stable
Description:default null values for not-null domains
Details:
create domain "D
On Tue, 30 Jan 2007, Tom Lane wrote:
"Sergiy Vyshnevetskiy" <[EMAIL PROTECTED]> writes:
Possible reason is forgotten SPI_push()/SPI_pop() wrapper in domain check
evaluation algorithm.
I think it's really plpgsql's fault, not the domain code. Try this patch:
http://archives.postgresql.org/pgs
