Doug McNaught wrote:
Leonel Nunez <lnunez@xxxxxxxxxxxxxx> writes:
You can use ByteA but the size will be about 4 times bigger
Are you sure? The intermediate form for bytea (escaped single-quoted
strings) is pretty inefficient, but once in the database the data is
stored as binary and can even be compressed.
Plus, I'm pretty sure the protocol supports transmitting bytea fields
as binary over the wire if your client software can handle it.
-Doug
I've made 2 pg_dumps from 2 different databases , 1 from a ByteA
stored images and 1 from the same images but stored as Base64 on
varchar and the
sql file for byteA was 4 times bigger than the size of all the
images on the Filesystem
and the sql for varchar with base64 was about 30% bigger than the
size on the filesystem
but If the bytea is encoded only for dump and load and on the
database are same size as the original file
then that's great and my perception is wrong
I'll check that
Leonel
