| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Anastasios Hatzis" <ahatzis(at)gmx(dot)net> |
| Cc: | <pgsql-general(at)postgresql(dot)org>, <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] Debugging SQL queries |
| Date: | 2006-05-11 14:23:50 |
| Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4013880E3@ratbert.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers pgsql-general |
> -----Original Message-----
> From: pgsql-general-owner(at)postgresql(dot)org
> [mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
> Sent: 11 May 2006 15:00
> To: Anastasios Hatzis
> Cc: pgsql-general(at)postgresql(dot)org; pgadmin-hackers(at)postgresql(dot)org
> Subject: Re: [GENERAL] Debugging SQL queries
>
> pgAdmin needs to catch up before 8.2 comes out ;-)
pgAdmin marks the line that the failure occurred at, and has done for
years. Whether or not it should dump the cursor at the exact location is
another issue altogether - it might upset ongoing editting (the user
could be editting or adding to the query whilst a long running part is
already running).
Regards, Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tony Caduto | 2006-05-11 14:39:59 | Re: [GENERAL] Debugging SQL queries |
| Previous Message | Tom Lane | 2006-05-11 14:00:17 | Re: [GENERAL] Debugging SQL queries |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tony Caduto | 2006-05-11 14:39:59 | Re: [GENERAL] Debugging SQL queries |
| Previous Message | Carlos Oliva | 2006-05-11 14:10:50 | Reindexdb |