| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Spaces in psql output (Was: FW: PGBuildfarm member snake Branch HEAD Status changed) |
| Date: | 2006-02-12 16:30:16 |
| Message-ID: | 17119.1139761816@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> About the ReportSyntaxErrorPosition thing, it was considered at the
> time (can't find the email right now) that control characters would be
> problematic but it wouldn't break anything that wasn't broken already.
> How tab was missed I don't know, nor a couple of other failures cases
> I've thought of since. Thanks for fixing that.
What I was thinking of doing was making it translate any control
character (other than \r and \n) to a space, not only tab. However
this should probably wait on the result of the discussion about whether
we really like the \x09 output for tabs in data ... that might yield an
idea that could be applied here too.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-02-12 16:35:21 | Re: [HACKERS] Spaces in psql output (Was: FW: PGBuildfarm |
| Previous Message | Tom Lane | 2006-02-12 16:18:03 | Re: Analyze and vacuum, they are sort of mandatory.... |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-02-12 16:35:21 | Re: [HACKERS] Spaces in psql output (Was: FW: PGBuildfarm |
| Previous Message | Tom Lane | 2006-02-12 16:19:45 | Re: psql tab completion enhancements |