Re: Processing very large TEXT columns (300MB+) using C/libpq

From: Geoff Winkless <pgsqladmin(at)geoff(dot)dj>
To: Geoff Winkless <pgsqladmin(at)geoff(dot)dj>
Cc: Bear Giles <bgiles(at)coyotesong(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Cory Nemelka <cnemelka(at)gmail(dot)com>, Aldo Sarmiento <aldo(at)bigpurpledot(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Processing very large TEXT columns (300MB+) using C/libpq
Date: 2017-10-23 10:17:42
Message-ID: CAEzk6fdjQFne3P0g+Xs+6LXHwoLY+aqjrkdm40j0xDh3DvVv1g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Randy Strauss 2017-10-23 22:14:28 Re: multiple sql results to shell
Previous Message Geoff Winkless 2017-10-23 09:36:00 Re: Processing very large TEXT columns (300MB+) using C/libpq