Hi Justin,
> Maybe I'm wrong, but I don't think there's any known difficulty - just that>
> nobody did it yet. You should pay attention to what happens on error, but
> hopefully you wouldn't need to add much code and can rely on existing code to
> paths to handle that right.
yes, I am trying t
>On Sat, Jun 06, 2020 at 09:23:32AM -0500, Justin Pryzby wrote:
> > On Wed, Jun 03, 2020 at 08:22:29PM +0800, 李杰(慎追) wrote:
> > > Partitioning is necessary for very large tables.
> > > However, I found that postgresql does not support create index
> > > concurrently on partitioned tables.
> > >
On Sat, Jun 06, 2020 at 09:23:32AM -0500, Justin Pryzby wrote:
> On Wed, Jun 03, 2020 at 08:22:29PM +0800, 李杰(慎追) wrote:
> > Partitioning is necessary for very large tables.
> > However, I found that postgresql does not support create index
> > concurrently on partitioned tables.
> > The document
On Wed, Jun 03, 2020 at 08:22:29PM +0800, 李杰(慎追) wrote:
> Partitioning is necessary for very large tables.
> However, I found that postgresql does not support create index concurrently
> on partitioned tables.
> The document show that we need to create an index on each partition
> individually a
Hi hackers,
Partitioning is necessary for very large tables.
However, I found that postgresql does not support create index concurrently on
partitioned tables.
The document show that we need to create an index on each partition
individually and then finally create the partitioned index non-conc
