| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Code bug or doc bug? |
| Date: | 2014-10-18 14:23:52 |
| Message-ID: | 20141018142352.GA16974@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 13, 2014 at 12:17:54PM -0400, Bruce Momjian wrote:
> On Wed, Aug 27, 2014 at 06:39:21AM -0700, David G Johnston wrote:
> > > Is there a doc patch to make here?
> >
> > 1. Last sentence change suggestion: "The target tablespace must be empty."
> >
> > 2. Based on Robert's comments it sounds like a "You cannot change the
> > default tablespace of the current database." comment should be added as
> > well.
> >
> > Side note: I have no clue what the "mapped relations" Robert refers to
> > are...
>
> I have created the attached doc patch for this. Should we backpatch
> this through 9.0, or just 9.4?
Applied.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Tiikkaja | 2014-10-18 14:29:41 | Re: get_actual_variable_range vs idx_scan/idx_tup_fetch |
| Previous Message | Bruce Momjian | 2014-10-18 13:58:10 | Re: get_actual_variable_range vs idx_scan/idx_tup_fetch |