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 CAEzk6fe8w+-MXxApaR5pAxCHmHRP=D2jgtBO0XwDu7Jew6aM=g@mail.gmail.com
Whole thread Raw
In response to Re: [ADMIN] Processing very large TEXT columns (300MB+) using C/libpq  (Bear Giles <bgiles@coyotesong.com>)
Responses Re: [ADMIN] Processing very large TEXT columns (300MB+) using C/libpq  (Bear Giles <bgiles@coyotesong.com>)
List pgsql-admin
On 20 October 2017 at 18:52, Bear Giles <bgiles@coyotesong.com> wrote:
As an aside any halfway decent optimizer would realize that the results of strlen() are unchanging as long as the contents of what it's passed isn't modified. That's a common enough pattern that it should be checked.

​IME this is a myth perpetuated by bad computer science lecturers who haven't thought through the consequences of what they're saying.​ strlen() can change because of changes inside the loop but also because of also threads in the system; I've not yet seen a compiler optimise that away, and neither should it, IMO.

G

pgsql-admin by date:

Previous
From: Bear Giles
Date:
Subject: Re: [ADMIN] Processing very large TEXT columns (300MB+) using C/libpq
Next
From: Bear Giles
Date:
Subject: Re: [ADMIN] Processing very large TEXT columns (300MB+) using C/libpq