| From: | SOzcn <selahattinozcnma(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Holger Jakobs <holger(at)jakobs(dot)com>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Reindex concurrently |
| Date: | 2023-12-13 18:52:02 |
| Message-ID: | CAJyV5Aa8kGuDD5z6RkKbTjA+V1nMiZZHkkZeRRCJxQ26WHJVYw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Cool!
I'll do it with bash. Cheers!
David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, 13 Ara 2023 Çar, 21:46
tarihinde şunu yazdı:
> On Wednesday,
>>
>> According to my research, the only way to do this is to write a bash
>> script in Linux and insert it with the loop.
>>
>
> Right. It is fundamentally impossible to store something in the database
> capable of executing multiple commands and not execute it within a normal
> transaction. The maintenance work that cannot be done within a transaction
> must be sourced externally and executed in an implicit transaction that
> auto-commits after the command finishes.
>
> David J.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2023-12-14 04:54:42 | Re: Verify data after backup and restore |
| Previous Message | Rajesh Kumar | 2023-12-13 18:49:36 | Re: Verify data after backup and restore |