Am Montag, 28. Juli 2003 15:53 schrieb Tom Lane:
> Philipp Reisner <[EMAIL PROTECTED]> writes:
> > If I execute this query several times (I receive the correct result set),
> > and then do an explain of the same query, the backend terminates with
> > sig 11 !!!
>
> Can you get us a debugger stack t
On Wed, 30 Jul 2003, sad wrote:
> good day
> we are suffering of the limit of parameters count in functions
> 16 parameters is not enough
What version are you using? I believe 7.3 raised the default to 32
and in all versions I've used there's a compile time define that can be
raised (look for
Philipp Reisner <[EMAIL PROTECTED]> writes:
> Program received signal SIGSEGV, Segmentation fault.
> 0x0812f9bc in DecodeDateTime ()
> (gdb) where
> #0 0x0812f9bc in DecodeDateTime ()
> Cannot access memory at address 0xbf003030
That's a fairly large routine :-(. Could I trouble you to rebuild w
Could you please confirm whether this behavior of PostgreSQL is a bug or a
feature?
Issue occurs wirh PostgreSQL 7.3.3
compiled with GCC 3.2.3
on aCeleron Coppermine 1100 MHz
powerd by Linux 2.4.21
I have two functions, one is called by a trigger
Patch applied. Thanks.
---
Thomas Behr wrote:
> Hej!
>
> select version();
>version
> --
> PostgreSQL 7
[EMAIL PROTECTED] writes:
> Now, the user-called function executes several INSERTS at once, and
> the trigger also is fired several times, but AFTER the complete
> function is done, and not after each specific INSERT, as I expected.
AFTER triggers fire at the end of the SQL statement.
Presently t
