Re: [ADMIN] Processing very large TEXT columns (300MB+) using C/libpq - Mailing list pgsql-admin

From Geoff Winkless
Subject Re: [ADMIN] Processing very large TEXT columns (300MB+) using C/libpq
Date
Msg-id CAEzk6fdjQFne3P0g+Xs+6LXHwoLY+aqjrkdm40j0xDh3DvVv1g@mail.gmail.com
Whole thread Raw
In response to Re: [ADMIN] Processing very large TEXT columns (300MB+) using C/libpq  (Geoff Winkless <pgsqladmin@geoff.dj>)
Responses Re: [ADMIN] Processing very large TEXT columns (300MB+) using C/libpq  (Bear Giles <bgiles@coyotesong.com>)
List pgsql-admin
I wrote:
> I assume that's because it can be certain at compile time that, since
> both buff and buff2 are local, nothing else is going to modify the
> source string (without some stack smashing, anyway).

Ugh. Of course, they're not local: they're malloc'd; however it's
still reasonable to assume that (since the pointers aren't passed
anywhere) the buffers are untouched elsewhere, unless other threads
are misbehaving.

Geoff


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

pgsql-admin by date:

Previous
From: Geoff Winkless
Date:
Subject: Re: [ADMIN] Processing very large TEXT columns (300MB+) using C/libpq
Next
From: Geoff Winkless
Date:
Subject: Re: [ADMIN] multiple sql results to shell