Apparently just leaving it alone until tomorrow managed to finish
creating/dropping the index. Thank you all very much.
On Thu, Aug 18, 2022 at 5:00 PM hubert depesz lubaczewski
wrote:
> On Thu, Aug 18, 2022 at 01:57:48PM +0800, Abdul Qoyyuum wrote:
> > Hi list,
> >
> > We have a running Master-
On Thu, Aug 18, 2022 at 01:57:48PM +0800, Abdul Qoyyuum wrote:
> Hi list,
>
> We have a running Master-Slave High Availability set up. Naturally, we
> can't run any changes on read-only databases on slave, so we have to do it
> on the master node.
>
> When trying to run the following command:
>
> On Aug 17, 2022, at 22:57, Abdul Qoyyuum wrote:
> Question is, do we have to shutdown traffic and close all existing open
> connections in order to drop and properly recreate the index?
No, you don't.
On the CREATE INDEX CONCURRENTLY command, what is likely going on is that when
the conne
Hi list,
We have a running Master-Slave High Availability set up. Naturally, we
can't run any changes on read-only databases on slave, so we have to do it
on the master node.
When trying to run the following command:
create index concurrently idx_cash_deposit_channel_id_batch_id on
cash_deposit
