Sam Mason <sam@xxxxxxxxxxxxx> writes: > As others have said; BYTEA is probably the best datatype for you to > use. The encoding of BYTEA literals is a bit of a fiddle and may need > some changes, but it's going to be much more faithful to your needs of > treating the filename as an opaque blob of data. bytea might be theoretically the best choice, but the fact remains that 99% of the entries will be text that's readable in the user's encoding (whatever that is). bytea will just be a serious PITA because of its escaping issues. Also, the fact that 8.5 may change to hex display by default will make bytea even more of a PITA for mostly-text data. So I think Bacula's choice to use sql_ascii with text columns is entirely defensible. What concerns me is the claim that PG made a database with some arbitrary parameters after having rejected a now-considered-invalid command. I frankly do not believe that, but if it did happen it's a *serious* bug that requires investigation. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
