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. 

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. 

Regards All, 
Lou Picciano 

----- Original Message -----
From: "Mantis Bug Tracker" <bugtr...@dbmail.org> 
To: dbmail-dev@dbmail.org 
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. 
====================================================================== 
http://www.dbmail.org/mantis/view.php?id=953 
====================================================================== 
Reported By: cmayo 
Assigned To: 
====================================================================== 
Project: DBMail 
Issue ID: 953 
Category: Database layer 
Reproducibility: have not tried 
Severity: tweak 
Priority: normal 
Status: new 
target: 
====================================================================== 
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 
per database 
Description: 
Update to INSTALL states PostgreSQL 9 users must set bytea_output = 
'escape' in postgresql.conf 
http://git.dbmail.eu/paul/dbmail/diff/INSTALL?id=cee2f2e9608b5866bb7cac01448d72718a8bc6ca
 

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 
their server. 

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. 

====================================================================== 

Issue History 
Date Modified Username Field Change 
====================================================================== 
23-Dec-11 16:44 cmayo New Issue 
====================================================================== 

_______________________________________________ 
Dbmail-dev mailing list 
Dbmail-dev@dbmail.org 
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev 
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev

Reply via email to