Re: [HACKERS] wrong sql statement crashes backend
Pavel Stehule [EMAIL PROTECTED] writes: SGVsbG8KCkkgZm91bmQgc2ltcGx5IGZ1bmN0aW9uIHdoaWNoIGlzIGJ1Z2d5 LCBidXQgaXQgY3Jhc2hlcyBzZXJ2ZXIKCkNSRUFURSBPUiBSRVBMQUNFIEZV TkNUSU9OIHRlc3QoYW55YXJyYXkpClJFVFVSTlMgYW55YXJyYXkgQVMgJCQK ICBTRUxFQ1QgJDFba107IC0tIGsgaXMgYnVnCiQkIExBTkdVQUdFIHNxbDsK ... Please don't send HTML-only email :-( Anyway, seems I broke this a couple months ago. Fixed, thanks for the report. regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] wrong sql statement crashes backend
Please don't send HTML-only email :-( I am sorry. It's stupid web mail. I didn't know so my messages was in html format. Anyway, seems I broke this a couple months ago. Fixed, thanks for the report. regards, tom lane ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] wrong sql statement crashes backend
Pavel Stehule wrote: Please don't send HTML-only email :-( I am sorry. It's stupid web mail. I didn't know so my messages was in html format. Actually, it looks to me like it was sent as plain text encoded as base64. I got: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by dunslane.net id l5HD4M6W030724 cheers andrew ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] wrong sql statement crashes backend
On 6/17/07, Andrew Dunstan [EMAIL PROTECTED] wrote: Pavel Stehule wrote: Please don't send HTML-only email :-( I am sorry. It's stupid web mail. I didn't know so my messages was in html format. Actually, it looks to me like it was sent as plain text encoded as base64. I got: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by dunslane.net id l5HD4M6W030724 gmail gives these two options for outgoing message encoding: Use default text encoding for outgoing messages Use Unicode (UTF-8) encoding for outgoing messages probably pavel had UTF-8 encoding -- regards, Jaime Casanova Programming today is a race between software engineers striving to build bigger and better idiot-proof programs and the universe trying to produce bigger and better idiots. So far, the universe is winning. Richard Cook ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly