| From: | Marti Raudsepp <marti(at)juffo(dot)org> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Log crashed backend's query (activity string) |
| Date: | 2011-09-07 21:09:32 |
| Message-ID: | CABRT9RCaMs_VeCB0Ljvpib=0u9VZVijcOYhwzKqFo-_fgifztw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 7, 2011 at 22:42, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> A mishandled encoding conversion could be problematic, so that needs to
> be carefully considered (perhaps just shut off unconditionally).
Are you referring to log file encoding or something else? The log file
is already potentially mixed-encoding, as different databases may have
different encodings and backends just dump bytes to it in their
current encoding.
pg_verify_mbstr() could potentially be used with noError=true if we
can figure out the backend's current encoding, but that indeed sounds
like something to avoid.
Regards,
Marti
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-09-07 21:16:08 | Re: timezone GUC |
| Previous Message | Tom Lane | 2011-09-07 20:55:24 | Re: FATAL: lock AccessShareLock on object 0/1260/0 is already held |