| From: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
|---|---|
| To: | veem v <veema0000(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Issue while creating index dynamically |
| Date: | 2024-07-25 07:55:33 |
| Message-ID: | CAFCRh--wrGmmpB7-er_FiXTY2BtRW6tXrWEzOQAj4RuWGnoZvQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jul 25, 2024 at 7:42 AM veem v <veema0000(at)gmail(dot)com> wrote:
> I was thinking the individual statement will work fine if I pull out those from the begin..end block, as those will then be not bounded by any outer transaction.
> However, When I was trying it from dbeaver by extracting individual index creation statements rather from within the "begin ..end;" block, it still failed with a different error as below. Why is it so?
>
> "SQL Error [25001]: Error: create index concurrently cannot be executed within a pipeline "
Perhaps it's an artifact of DBeaver using [LibPQ's pipeline mode][1]
when executing scripts?
Maybe give it a try in `psql` instead. Or find a setting to disable
pipeline mode? (which is new to v14).
[1]: https://www.postgresql.org/docs/current/libpq-pipeline-mode.html
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christian Schröder | 2024-07-25 10:58:55 | RE: Memory issues with PostgreSQL 15 |
| Previous Message | Konstantin Berkaev | 2024-07-25 05:42:34 | Re: Support logical replication of DDLs |