Re: PLPGSQL - store fetched records in array of record

From: Durumdara <durumdara(at)gmail(dot)com>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: PLPGSQL - store fetched records in array of record
Date: 2025-07-02 14:26:39
Message-ID: CAEcMXhmHuVg7kbcqekULOxckOYZRaTHkO4Es8vJeUQAT2wyJPg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

Sorry.
I forgot to mention that I have two arrays (records).

One for the modifiable elements, and one for the checkable elements.

If there is a conflict between the actual mod. item and one of the
checkable items, the checkable item will move to the end of the
modification list.
And the actual mod. item starting time could be changed in this process.

First I imagined a temporary table, but I felt this has too much overhead
against an "in memory" array.
UPDATE, INSERT, DELETE and reopen after each modification.

Ron Johnson <ronljohnsonjr(at)gmail(dot)com> ezt írta (időpont: 2025. júl. 2.,
Sze, 15:29):

> On Wed, Jul 2, 2025 at 8:21 AM Durumdara <durumdara(at)gmail(dot)com> wrote:
>
>> Hello!
>>
>> I have to store some fetched records into two lists (arrays) to work with
>> them.
>>
>
> There's almost certainly a way to do what you need done without using
> arrays. Might require a bit of rethinking, though.
>
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> lobster!
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Franklin Anderson de Oliveira Souza 2025-07-02 14:32:51 Re: Simulate a PITR in postgresql 16
Previous Message Ron Johnson 2025-07-02 13:29:03 Re: PLPGSQL - store fetched records in array of record