Re: [PATCHES] Proposed patch for error locations

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Glaesemann <grzm(at)myrealbox(dot)com>, pgsql-patches(at)postgresql(dot)org, pgsql-interfaces(at)postgresql(dot)org
Subject: Re: [PATCHES] Proposed patch for error locations
Date: 2006-03-14 02:53:19
Message-ID: 4416301F.9070800@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces pgsql-patches

> from all libpq-using applications not just psql. We could make this
> conditional on the error verbosity --- in "terse" mode the "LINE N"
> output wouldn't appear, and "at character N" still would. Applications
> should already be expecting multiline outputs from PQerrorMessage if
> they're in non-terse mode, so this ought to be OK. Comments?

Sounds like it'd be handy in phpPgAdmin...

In response to

Browse pgsql-interfaces by date

  From Date Subject
Next Message Evan Sherwood 2006-03-16 07:39:18 Postgres - problems with NpgsqlDataAdapter insert
Previous Message Fangbing Wu 2006-03-14 01:25:46 Inherits and triggers

Browse pgsql-patches by date

  From Date Subject
Next Message Simon Riggs 2006-03-14 08:55:40 Re: [PATCHES] Automatic free space map filling
Previous Message Tom Lane 2006-03-13 21:28:38 Re: [PATCHES] Proposed p.tch for error locations