"Tanya Mamedalin" <[EMAIL PROTECTED]> writes:
> Sorry, I wasn't sure how much information I should provide. To be thorough:
Thanks for the background. I tried the query with these table
definitions and it didn't crash for me. This may mean that the bug is
fixed in 7.4.1, or it might just mean t
t;outages" to "postgres";
GRANT INSERT,SELECT,UPDATE,DELETE on "outages" to "ops2";
GRANT INSERT,SELECT on "outages" to GROUP "operators";
GRANT ALL on "outages" to GROUP "opsadmins";
--
-- TOC Entry ID 19 (OID 16580)
--
-- Name:
"Tanya Mamedalin" <[EMAIL PROTECTED]> writes:
> I was running the same Python code with Postgres 7.2.3 and psycopg 1.0.9
> with no errors. As soon as I upgraded to Postgres 7.4-0.3 and pyscopg 1.1.6
> I started getting errors when trying to execute a certain query.
BTW, this might be the same bug
"Tanya Mamedalin" <[EMAIL PROTECTED]> writes:
> Possible ways to reproduce the error: Run a multipart query similar to:
> SELECT DISTINCT o.outage_id, o.machine, o.service, o.level, o.comments,
> o2.time, e.num
>FROM outages o, outages o2, escalation e
>WHERE o.outage_id='31009'
>
POSTGRESQL BUG REPORT TEMPLATE
Your name : Tanya Mamedalin
Your email address : [EMAIL PROTECTED]
