Re: python patch - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: python patch
Date
Msg-id GNELIHDDFBOCMGBFGEFOCEKACDAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to Re: python patch  (Greg Copeland <greg@CopelandConsulting.Net>)
Responses Re: python patch
List pgsql-hackers
> Not a problem.  I would rather them be correct.
>
> Worth noting that the first patch is what attempts to fix the long ->
> int overflow issue.  The second patch attempts to resolve "attisdropped"
> column use issues with the python scripts.  The third patch addresses
> issues generated by the implicate to explicate use of "cascade".
>
> I assume your reservations are only with the second patch and not the
> first and third patches?

Correct.  I'm pretty sure you don't need to exclude attisdropped from the
primary key list because all it's doing is finding the column that a primary
key is over and that should never be over a dropped column.  I can't
remember what you said the second query did?

Chris



pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: [GENERAL] workaround for lack of REPLACE() function
Next
From: "Christopher Kings-Lynne"
Date:
Subject: Re: [SECURITY] DoS attack on backend possible (was: Re: