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

From Bear Giles
Subject Re: [ADMIN] Processing very large TEXT columns (300MB+) using C/libpq
Date
Msg-id CALBNtw5qg71eZbVOVx2rKgrRrN6_h85h+TOXpDbyQr2nANFYfQ@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>)
List pgsql-admin
I meant the developer needs to add the locks, not the compiler. I think they're just advisory but everyone always rights well-behaved code, right? ;-)

On Mon, Oct 23, 2017 at 4:17 AM, Geoff Winkless <pgsqladmin@geoff.dj> wrote:
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

pgsql-admin by date:

Previous
From: Geoff Winkless
Date:
Subject: Re: [ADMIN] multiple sql results to shell
Next
From: "Ferrell, Denise D CTR NSWCDD, H11"
Date:
Subject: [ADMIN] Database Error