| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Greg Copeland" <greg(at)copelandconsulting(dot)net> |
| Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "PostgresSQL Hackers Mailing List" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: python patch |
| Date: | 2002-08-12 02:15:16 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOCEKACDAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2002-08-12 02:25:18 | Re: [SECURITY] DoS attack on backend possible (was: Re: |
| Previous Message | Tatsuo Ishii | 2002-08-12 01:07:20 | Re: [GENERAL] workaround for lack of REPLACE() function |