loupicciano at comcast
Dec 23, 2011, 8:14 AM
Post #2 of 3
Actually, the bytea_output is probably best set in the specific (DBmail) session - this is a capability of PostgreSQL. Getting even fancier, it can easily be set on a per-function or per-transaction basis - though I don't think DBmail itself has any need of this granularity.
Re: [DBMail 0000953]: Make PostgreSQL 9 users aware bytea format can be per database
[In reply to]
Specifically, it would be imprudent to ALTER DATABASE, as this will affect all output from the _entire_ database, and may break many things. Many PG users are making the full transition to hex format - the new default - and many of us incorporate dbmail into 'larger context' databases for many purposes.
Thanks again, Paul, for all your hard work.
----- Original Message -----
From: "Mantis Bug Tracker" <bugtrack [at] dbmail>
To: dbmail-dev [at] dbmail
Sent: Friday, December 23, 2011 10:44:19 AM
Subject: [Dbmail-dev] [DBMail 0000953]: Make PostgreSQL 9 users aware bytea format can be per database
The following issue has been SUBMITTED.
Reported By: cmayo
Issue ID: 953
Category: Database layer
Reproducibility: have not tried
Date Submitted: 23-Dec-11 16:44 CET
Last Modified: 23-Dec-11 16:44 CET
Summary: Make PostgreSQL 9 users aware bytea format can be
Update to INSTALL states PostgreSQL 9 users must set bytea_output =
'escape' in postgresql.conf
I believe this can also be done just for the dbmail database with:
ALTER DATABASE dbmail SET bytea_output='escape';
which would probably be preferable for people with other databases on
Doesn't look like it exists in pre 9.0 PostgreSQL though so maybe not a
good candidate for the database schema itself yet.
Good to have the update to INSTALL - I had thought this was just needed
during dbmail upgrade.
Date Modified Username Field Change
23-Dec-11 16:44 cmayo New Issue
Dbmail-dev mailing list
Dbmail-dev [at] dbmail