| From: | Michael Moore <michaeljmoore(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | postgres list <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: Updating jsonb rows |
| Date: | 2017-08-14 19:33:18 |
| Message-ID: | CACpWLjPhwbSC-BJ3dNrcAFu1FYH4rrJ7n-0t+FzacOJ68SeisA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Probably the solution is "don't try to use JSON as temp tables for anything
but very small datasets". As you know, I'm converting an application that
uses temp tables to NOT use temp tables because it needs to run in a
read-only database. JSONB seemed to be the way to go because you can almost
treat them the same as temp tables. I think in the end, it will be "fast
enough", but just not as fast as temp tables. Thanks for your help!
Mike
On Mon, Aug 14, 2017 at 11:12 AM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Mon, Aug 14, 2017 at 10:35 AM, Michael Moore <michaeljmoore(at)gmail(dot)com>
> wrote:
>
>> Basically what I am doing is trying to simulate a SQL UPDATE statement.
>> currently I am doing this, and* it works, but it is slow*, so I am
>> looking for a better way.
>>
>
> I don't presently know a better solution in PostgreSQL.
>
> Dave
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Moore | 2017-08-14 20:51:32 | Re: Updating jsonb rows |
| Previous Message | David G. Johnston | 2017-08-14 18:12:54 | Re: Updating jsonb rows |