| From: | Asya Nevra Buyuksoy <ayisan1096(at)gmail(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Luís Roberto Weck <luisroberto(at)siscobra(dot)com(dot)br>, Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Fwd: TOAST table performance problem |
| Date: | 2020-02-10 12:59:42 |
| Message-ID: | CADA48rEeoM-S5a0kk6j_t26TLoJnqHhjYRRZgLO1oi1qjJhMNg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Ok, you are right. Thanks for everything.
Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, 10 Şub 2020 Pzt, 15:54 tarihinde şunu
yazdı:
> On Mon, Feb 10, 2020 at 7:38 AM Asya Nevra Buyuksoy <ayisan1096(at)gmail(dot)com>
> wrote:
>
>> Got it, thanks! I understand and know it that PostgreSQL is not slow, but
>> I want to a piece of advice how can I load this data fastly :)
>>
>
> You haven't told us anything about your client, so what advice can we
> offer? Unless the bottleneck is in the libpq library, this is probably not
> the right place to ask about it anyway.
>
> Cheers,
>
> Jeff
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-02-10 15:39:31 | Re: Bad selectivity estimate when using a sub query to determine WHERE condition |
| Previous Message | Jeff Janes | 2020-02-10 12:53:57 | Re: Fwd: TOAST table performance problem |