| From: | Michael Meskes <meskes(at)postgresql(dot)org> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Michael Meskes <meskes(at)postgresql(dot)org>, PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ecpg leaves broken files around |
| Date: | 2007-06-11 06:05:16 |
| Message-ID: | 20070611060516.GA30692@feivel.credativ.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jun 10, 2007 at 09:56:44PM +0200, Magnus Hagander wrote:
> AFAIK, most other compilers delete their output if it's not valid. Is
> there any particular reason why ecpg doesn't do this?
No, not really. Sometimes it comes handy to see what was already
processed, but you're right, it's not what I would expect from a
compiler either.
Any objects changing this behaviour?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ITAGAKI Takahiro | 2007-06-11 06:27:48 | Re: Controlling Load Distributed Checkpoints |
| Previous Message | Bruce Momjian | 2007-06-11 02:20:30 | Re: Stats not updated after rollback -- autovacuum confused. |