https://www.postgresql.org/docs/current/ddl-partitioning.html provides an
example of using CONCURRENTLY for index creation of partitioned tables; but
it the example itself doesn't have this word; here is a fix:
diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index
4490e82aa52f3c0e203904
Curious: why plv8 is still not in the core distro?
(apologies for top posting)
On Fri, Jul 16, 2021 at 6:35 AM Tom Lane wrote:
> PG Doc comments form writes:
> >> If you have pattern matching needs that go beyond this, consider
> writing a
> >> user-defined function in Perl or Tcl.
>
> > If yo
diff --git a/doc/src/sgml/indices.sgml b/doc/src/sgml/indices.sgml
index
671299ff059d972ff95bdb1d67ed4c89bf5040b2..c7eaf9a608e995ef9957b4e0f677b36a8303be55
100644
--- a/doc/src/sgml/indices.sgml
+++ b/doc/src/sgml/indices.sgml
@@ -741,6 +741,15 @@ CREATE INDEX people_names ON people ((first_name
|
On Sun, Mar 7, 2021 at 08:43 Tom Lane wrote:
> Apparently, you didn't install whichever sub-package of the Postgres
> distribution contains pg_config. Might be postgresql-devel, or
> postgresql-dev in Debian-flavored distros. The PG project documentation
> can't cover this; it's the responsibil
A follow-up on this:
Should documentation also mention that it does not make sense to set
effective_cache_size < shared_buffers? And maybe it is worth prohibiting
this or at least having a WARNING in logs?
Why: I see setups where with growing RAM and shared_buffers set to 25%,
effective_cache_siz
Related:
https://www.postgresql.org/message-id/flat/20160730001838.GA22405%40momjian.us#ef946043c336d66e717e0e6e96639f92
Although, 3 years passed since then. I constantly see "kiB", "MiB", etc in
many discussions. And some very popular programs already migrated to it.
For example, in Linux, "top"
On Mon, Nov 5, 2018 at 3:01 PM Bruce Momjian wrote:
> > > {"effective_cache_size", PGC_USERSET, QUERY_TUNING_COST,
> > > - gettext_noop("Sets the planner's assumption about
> the size of the disk cache."),
> > > - gettext_noop("That is, the portion
On Thu, Oct 25, 2018 at 6:03 AM Jehan-Guillaume de Rorthais
wrote:
> What about logging the shutdown checkpoint on the old master?
> On the standby side, we could cross-check it with a function confirming:
> 1/ the very last XLogRecord received was the old master shutdown checkpoint
> 2/ the rece
Currently, the documentation explicitly states, that after failover, the
old master must be recreated from scratch, or pg_rewind should be used
(requiring wal_log_hints to be on, which is off by default):
> The former standby is now the primary, but the former primary is down and
might stay down.
Hi,
On Sun, Jul 29, 2018 at 8:54 AM PG Doc comments form
wrote:
> From where I can download Postgresql documentation of PDF format.
>
You can do it here: https://www.postgresql.org/docs/manuals/
10 matches
Mail list logo