On Wed, Aug 17, 2022 at 06:09:13PM +0300, Максим Яблоков wrote:
> I have prepared a small patch with possible changes of these places, and
> also a separate patch with some improvements concerning missed/inapt tags.
> Please have a look.
archive_command is used only when archive_library is not set
On Wed, Aug 17, 2022 at 05:11:23PM -0400, Jeff Janes wrote:
> That looks good to me. But now looking over the linked pages more, it seems
> like https://www.postgresql.org/docs/current/indexes-types.html was never
> changed to admit the possibility of custom index access methods (like bloom)
Uh,
> On 17 Aug 2022, at 23:24, Bruce Momjian wrote:
>
> On Wed, Aug 17, 2022 at 10:58:55PM +0200, Daniel Gustafsson wrote:
>>> On 17 Aug 2022, at 22:56, Bruce Momjian wrote:
>>
>>> Is there a reason this patch was not applied?
>>
>> Only that it fell of my radar, if you think it's adding value I'
On Wed, Aug 17, 2022 at 10:58:55PM +0200, Daniel Gustafsson wrote:
> > On 17 Aug 2022, at 22:56, Bruce Momjian wrote:
>
> > Is there a reason this patch was not applied?
>
> Only that it fell of my radar, if you think it's adding value I'm happy to get
> it done now.
Sure, it looked useful to m
On Wed, Aug 17, 2022 at 2:58 PM Bruce Momjian wrote:
> On Wed, Aug 17, 2022 at 12:41:03PM -0400, Jeff Janes wrote:
> > This was recently added to CREATE INDEX reference page:
> >
> > +The optional USING clause specifies an index
> > +type as described in . If not
> > +spe
> On 17 Aug 2022, at 22:56, Bruce Momjian wrote:
> Is there a reason this patch was not applied?
Only that it fell of my radar, if you think it's adding value I'm happy to get
it done now.
--
Daniel Gustafsson https://vmware.com/
Is there a reason this patch was not applied?
---
On Fri, Nov 12, 2021 at 02:46:40PM +0100, Daniel Gustafsson wrote:
> > On 22 Oct 2021, at 13:12, PG Doc comments form
> > wrote:
> >
> > The following documentation comme
On Fri, Oct 22, 2021 at 11:55:33AM -0700, Kevin Sweet wrote:
> The bugs team agreed that it's a bug. The documentation accurately represents
> the buggy code. I thought you might want to update the doc when the bug is
> fixed.
This was fixed in this commit:
commit 5fcf3945bd
Autho
In looking at CREATE STATISTICS, I was confused how inheritance and
partisions were handled, so I confirmed with Tomas that the ANALYZE
manual page accurately describes how extended statistics are handled
since PG 15, so I plan to apply this patch to the CREATE STATISTICS
docs.
--
Bruce Momjian
On Wed, Aug 17, 2022 at 12:41:03PM -0400, Jeff Janes wrote:
> This was recently added to CREATE INDEX reference page:
>
> + The optional USING clause specifies an index
> + type as described in . If not
> + specified, a default index type will be used based on the
> +
This was recently added to CREATE INDEX reference page:
+The optional USING clause specifies an index
+type as described in . If not
+specified, a default index type will be used based on the
+data types of the columns.
But I think this is wrong, the default type
On Sat, Oct 23, 2021 at 01:51:48PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/14/tutorial-agg.html
> Description:
>
> currently, all of the examples are very simple, like
>
> SELECT city, max(
Hello!
I’ve noticed that some changes concerning replacement of archive_command
by archive_library in the documentation for PostgreSQL 15 do not quite
fit in:
1. https://www.postgresql.org/docs/15/continuous-archiving.html
Archiving of these files happens automatically since you have already
On Mon, Nov 1, 2021 at 01:23:01PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/14/view-pg-stats-ext.html
> Description:
>
> When table mytable is being inherited it may not contain any data but
14 matches
Mail list logo
