Tom Lane wrote:
Klint Gore <[EMAIL PROTECTED]> writes:
> David Wilson wrote:
>> I'm not certain how to check the actual byte width of a column within a
>> row,
> select length(bytea_field) from table
If you want the actual on-disk footprint, use pg_column_size()
Size on disk would have the
Klint Gore <[EMAIL PROTECTED]> writes:
> David Wilson wrote:
>> I'm not certain how to check the actual byte width of a column within a
>> row,
> select length(bytea_field) from table
If you want the actual on-disk footprint, use pg_column_size()
regards, tom lane
--
Se
David Wilson wrote:
On Mon, Jul 28, 2008 at 1:24 AM, Klint Gore <[EMAIL PROTECTED]> wrote:
> Try just a single \
>
> e.g.
> "ge.xls","application/vnd.ms-excel",71168,"\320\317\021\340\241[snip]
Thanks- I did try that, and it at least gave the expected output from
select, but is there a way to ve
On Mon, Jul 28, 2008 at 1:24 AM, Klint Gore <[EMAIL PROTECTED]> wrote:
> Try just a single \
>
> e.g.
> "ge.xls","application/vnd.ms-excel",71168,"\320\317\021\340\241[snip]
Thanks- I did try that, and it at least gave the expected output from
select, but is there a way to verify that it's actuall
David Wilson wrote:
My application is adding a bytea column to a table into which data is
dumped in approximately 4k row batches, one batch approximately every
10 seconds. To this point, those dumps have used copy from stdin;
however, I'm having some difficulty getting bytea encodings to work
wit
My application is adding a bytea column to a table into which data is
dumped in approximately 4k row batches, one batch approximately every
10 seconds. To this point, those dumps have used copy from stdin;
however, I'm having some difficulty getting bytea encodings to work
with it. Specifically, I
