From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Andreas Joseph Krogh <andreas(at)visena(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: which work memory parameter is used for what? |
Date: | 2016-11-09 16:07:14 |
Message-ID: | CAKFQuwb5VLim58XHBYGQ50q26_tNzSKjFL_+rX1zNXmEatGggw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Nov 9, 2016 at 7:54 AM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 11/08/2016 06:45 PM, Andreas Joseph Krogh wrote:
> > På onsdag 09. november 2016 kl. 03:02:54, skrev John R Pierce
> >
> >
> > https://www.postgresql.org/docs/current/static/runtime-
> config-resource.html
> >
> >
> > maintenance_work_mem is used by vacuum and create index operations
> > (including implicit index creation such as add foreign key).
> >
> >
> > There is no such thing in PG.
>
> Can you be more specific as;
>
> https://www.postgresql.org/docs/9.5/static/runtime-
> config-resource.html#GUC-MAINTENANCE-WORK-MEM
>
>
I suppose that "
ALTER TABLE ADD FOREIGN KEY
" uses maintenance_work_mem while executing the query necessary to confirm
that for every distinct value in the new foreign key there exists a
corresponding primary key. The PK already has an associated index because
of an implementation detail enforcing uniqueness. The foreign key has no
need for such an artifact.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Melvin Davidson | 2016-11-09 16:11:15 | Re: which work memory parameter is used for what? |
Previous Message | Andreas Joseph Krogh | 2016-11-09 15:05:42 | Re: which work memory parameter is used for what? |