Tom Lane wrote:
Eric E <[EMAIL PROTECTED]> writes:
Here's the test function:
...
my $data_handle = spi_exec_query('SELECT * FROM
schema1."table_of_approximately 3 rows";');
Well, the plperl documentation does point out that spi_exec_query should
only be used when you know that t
Eric E <[EMAIL PROTECTED]> writes:
> Here's the test function:
> ...
> my $data_handle = spi_exec_query('SELECT * FROM
> schema1."table_of_approximately 3 rows";');
Well, the plperl documentation does point out that spi_exec_query should
only be used when you know that the result set will be
Hi Tom,
It was a backend crash on my production 7.4 instance, running on Suse
Linux 9.1 Pro, installed from Suse's precompiled binaries, on what turns
out to be questionable hardware.
I wrote a PL/PERL function specifically to crash the database in this
way, and ran it against a test instance
Eric E <[EMAIL PROTECTED]> writes:
> I've recently had a couple worrisome experiences with runaway
> queries in postgres 7.4 and 8.0, and I'm wondering what I can do to
> control or prevent these. When I ran a query against a large table, I
> accidentally omitted mistyped a table name, and
