Re: plpgsql function with offset - Postgres 9.1

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Patrick B <patrickbakerbr(at)gmail(dot)com>
Cc: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: plpgsql function with offset - Postgres 9.1
Date: 2017-06-15 22:53:00
Message-ID: CAKFQuwbLBZrcEfP+GgAS-TLh_oZmz6HUtMXcpKAxErD3UU1jSg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Jun 15, 2017 at 3:49 PM, Patrick B <patrickbakerbr(at)gmail(dot)com> wrote:

> 2017-06-16 10:35 GMT+12:00 David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>:
>
>> On Thu, Jun 15, 2017 at 3:19 PM, Patrick B <patrickbakerbr(at)gmail(dot)com>
>> wrote:
>>
>>> 2017-05-29 19:27 GMT+12:00 Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>:
>>>
>>>> Patrick B wrote:
>>>> > I am running a background task on my DB, which will copy data from
>>>> tableA to tableB. For
>>>> > that, I'm writing a PL/PGSQL function which basically needs to do the
>>>> following:
>>>> >
>>>
>>>
>> ​https://www.postgresql.org/message-id/CY1PR18MB0490632A9A73
>> E64973F66D6BAFCE0%40CY1PR18MB0490.namprd18.prod.outlook.com
>>
>> My problem is when using LIMIT to select the data I get none. I assume
> because the first 3000 rows (i'm using ORDER BY 1) are not candidates for
> the migration.
>

Your where clause should only allow candidates to be selected. If it does
then your theory is wrong.

David J.​

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2017-06-15 23:03:07 Re: Connection options
Previous Message Patrick B 2017-06-15 22:49:19 Re: plpgsql function with offset - Postgres 9.1