|From:||Stephen Frost <sfrost(at)snowman(dot)net>|
|To:||Heikki Linnakangas <hlinnaka(at)iki(dot)fi>|
|Cc:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ian Lawrence Barwick <barwick(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: [doc] remove reference to pg_dump pre-8.1 switch behaviour|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
* Heikki Linnakangas (hlinnaka(at)iki(dot)fi) wrote:
> On 23/10/2020 17:51, Tom Lane wrote:
> >But anyway, this was about documentation not code. What I'm wondering
> >about is when to drop things like, say, this bit in the regex docs:
> > Two significant incompatibilities exist between AREs and the ERE syntax
> > recognized by pre-7.4 releases of <productname>PostgreSQL</productname>:
> > (etc etc)
> >Seems like we could have gotten rid of that by now, but when exactly
> >does it become fair game? And can we have a non-ad-hoc process for
> >getting rid of such cruft?
> Let's try to zoom in on a rule:
> Anything that talks about 9.4 or above (min supported version - 1) should
> definitely be left in place.
> Something around 9.0 is possibly still useful to someone upgrading or
> updating an application. Or someone might still bump into old blog posts
> from that era.
Right- going back ~10 years. (I do think it'd be good to have an actual
policy rather than just "well, right now, it seems like 9.0 is about
> Before that, I don't see much value. Although you could argue that I jumped
> the gun on the notice about pre-8.2 pg_dump -t behavior. pg_dump still
> supports servers down to 8.0, so someone might also have an 8.0 pg_dump
> binary lying around, and might be confused that -t behaves differently. On
> the whole though, I think removing it was fair game.
I don't really have an issue with it, to be clear. I had been hoping we
might be able to come up with a general rule to apply across both
documentation and code (in particular, pg_dump), but that doesn't seem
to be the case. That does mean that *some* documentation might end up
needing to keep notes from before 9.0, where that documentation is about
pg_dump and older versions.
> I did some grepping for strings like "version 7", "pre-8" and so on. I
> couldn't come up with a clear rule on what could be removed. Context
> matters. In text that talks about protocol versions or libpq functions like
> PQlibVersion() it seems sensible to go back as far as possible, for the
> completeness. And subtle user-visible differences in behavior are more
> important to document than changes in internal C APIs that cause a compiler
> failure, for example.
I agree that context matters.
> Other notices are about old syntax that's kept for backwards compatibility,
> but still works. It makes sense to mention the old version in those cases,
> even if it's very old, because the alternative would be to just say
> something like "very old version", which is not any shorter, just less
I would argue that we shouldn't be keeping things around for backwards
compatibility, in general. If we feel that it's a good feature to keep
then let's keep it and just document it as an alternative syntax.
> Findings in detail follow. And attached is a patch about the stuff that I
> think can be removed pretty straightforwardly.
Thanks a lot for spending the time going through all of this!
> If the value written for an element is <literal>NULL</literal> (in any
> variant), the element is taken to be NULL. The presence of any quotes
> or backslashes disables this and allows the literal string value
> <quote>NULL</quote> to be entered. Also, for backward compatibility with
> pre-8.2 versions of <productname>PostgreSQL</productname>, the <xref
> linkend="guc-array-nulls"/> configuration parameter can be turned
> <literal>off</literal> to suppress recognition of <literal>NULL</literal>
> as a NULL.
> The GUC still exists, so we should keep this.
I agree we should keep the documentation as long as the GUC exists- but
we should be considering getting rid fo the GUC.
> The view <structname>pg_group</structname> exists for backwards
> compatibility: it emulates a catalog that existed in
> <productname>PostgreSQL</productname> before version 8.1.
> It shows the names and members of all roles that are marked as not
> <structfield>rolcanlogin</structfield>, which is an approximation to the
> of roles that are being used as groups.
> pg_group still exists, and that paragraph explains why. We should keep it.
> (There's a similar paragraph for pg_shadow)
When I wrote that, many many years ago (apparently about 15, looking
back at the commit responsible), I certainly didn't expect we'd still
have them today. These views, which have been only haphazardly
maintained and which don't really represent the current system terribly
well, need to go. In hindsight, introducing them was a mistake in the
first place. We support 5 major versions for a reason and people should
be updating their code as we make changes- as they have to do in lots of
other parts of the system and for other catalogs (consider the v10
changes of XLOG -> WAL).
If we keep the views we should keep the documentation, of course, but
it's long, long past time to rip out pg_user, pg_group, and pg_shadow.
Now that we have column-level privileges, I'd think we could probably
get rid of pg_roles too as not really providing much value.
> config.sgml (on synchronized_scans):
> This allows sequential scans of large tables to synchronize with
> other, so that concurrent scans read the same block at about the
> same time and hence share the I/O workload. When this is enabled,
> a scan might start in the middle of the table and then <quote>wrap
> around</quote> the end to cover all rows, so as to synchronize with
> activity of scans already in progress. This can result in
> unpredictable changes in the row ordering returned by queries that
> have no <literal>ORDER BY</literal> clause. Setting this parameter
> <literal>off</literal> ensures the pre-8.3 behavior in which a
> scan always starts from the beginning of the table. The default
> is <literal>on</literal>.
> We could remove the reference to 8.3 version. I'm inclined to keep it
I'm fine keeping the reference, if we keep the GUC. I'm not really
inclined to keep this GUC though, at least not for the purpose of having
it to match pre-8.3 behavior explicitly. If there's some usefulness to
this GUC then we should document what that is. If there isn't, then
let's remove it.
> func.sgml (String Functions and Operators):
> Before <productname>PostgreSQL</productname> 8.3, these functions would
> silently accept values of several non-string data types as well, due to
> the presence of implicit coercions from those data types to
> <type>text</type>. Those coercions have been removed because they
> caused surprising behaviors. However, the string concatenation
> (<literal>||</literal>) still accepts non-string input, so long as at
> least one
> input is of a string type, as shown in <xref
> linkend="functions-string-sql"/>. For other cases, insert an explicit
> coercion to <type>text</type> if you need to duplicate the previous
> Could remove the reference to 8.3, but the information about || still makes
> sense. I'm inclined to just keep it.
I'd rather we rip out what the pre-8.3 behavior was as no longer
relevant and shorten this up quite a bit:
The string concatenation operator (<literal>||</literal>) will accept
non-string input, so long as at least one input is of string type, as
shown in <xref linkend="functions-string-sql"/>. For other cases,
inserting an explicit coercion to <type>text</type> can be used to have
non-string input accepted.
We're talking about v14 for this, after all.
> Before <productname>PostgreSQL</productname> 8.2, the containment
> operators <literal>@></literal> and <literal><@</literal> were
> called <literal>~</literal> and <literal>@</literal>. These names are
> available, but are deprecated and will eventually be removed.
> The old names are still available, so should keep this.
We should either remove them, or document them directly as alternative
spellings and admit to ourselves that they aren't deprecated and aren't
going to be removed.
> Before <productname>PostgreSQL</productname> 8.1, the arguments of the
> sequence functions were of type <type>text</type>, not
> <type>regclass</type>, and
> the above-described conversion from a text string to an OID value would
> happen at run time during each call. For backward compatibility, this
> facility still exists, but internally it is now handled as an implicit
> coercion from <type>text</type> to <type>regclass</type> before the
> function is
> Let's remove this.
> <xref linkend="array-operators-table"/> shows the specialized operators
> available for array types.
> In addition to those, the usual comparison operators shown in <xref
> linkend="functions-comparison-op-table"/> are available for
> arrays. The comparison operators compare the array contents
> element-by-element, using the default B-tree comparison function for
> the element data type, and sort based on the first difference.
> In multidimensional arrays the elements are visited in row-major order
> (last subscript varies most rapidly).
> If the contents of two arrays are equal but the dimensionality is
> different, the first difference in the dimensionality information
> determines the sort order. (This is a change from versions of
> <productname>PostgreSQL</productname> prior to 8.2: older versions would
> that two arrays with the same contents were equal, even if the
> number of dimensions or subscript ranges were different.)
> Could remove it.
+1 to remove.
> There are two differences in the behavior of
> from pre-9.1 versions of <productname>PostgreSQL</productname>.
> First, it will return an empty (zero-element) array rather
> than <literal>NULL</literal> when the input string is of zero length.
> Second, if the delimiter string is <literal>NULL</literal>, the
> splits the input into individual characters, rather than
> returning <literal>NULL</literal> as before.
> Feels too early to remove.
+0 to remove, for my part.
> Prior to <productname>PostgreSQL</productname> 8.2, the
> <literal><</literal>, <literal><=</literal>,
> <literal>></literal> and <literal>>=</literal>
> cases were not handled per SQL specification. A comparison like
> <literal>ROW(a,b) < ROW(c,d)</literal>
> was implemented as
> <literal>a < c AND b < d</literal>
> whereas the correct behavior is equivalent to
> <literal>a < c OR (a = c AND b < d)</literal>.
> Important incompatibility. Although very old. I'm inclined to keep it. If we
> remove it, it'd still be useful to explain the new behavior.
+1 to remove and replace with an explanation of the new behavior.
> <title>GIN Tips and Tricks</title>
> <term>Create vs. insert</term>
> Insertion into a <acronym>GIN</acronym> index can be slow
> due to the likelihood of many keys being inserted for each item.
> So, for bulk insertions into a table it is advisable to drop the GIN
> index and recreate it after finishing bulk insertion.
> As of <productname>PostgreSQL</productname> 8.4, this advice is less
> necessary since delayed indexing is used (see <xref
> linkend="gin-fast-update"/> for details). But for very large updates
> it may still be best to drop and recreate the index.
> I think that's old enough, but the paragraph would need some copy-editing,
> not just removal.
Building a <acronym>GIN</acronym> index after all of the data has been
loaded will typically be faster than creating the index and then filling
it. There may also be cases where, for a sufficiently large update,
dropping the <acronym>GIN</acronym> index, then performing the update,
and then recreating the index will be faster than a routine update,
however, one should review the delayed indexing technique used for
<acronym>GIN</acronym> (see <xref linkend="gin-fast-update"/> for
details) and the options it provides.
> high-availability.sgml (Record-based log shipping)
> <sect2 id="warm-standby-record">
> <title>Record-Based Log Shipping</title>
> It is also possible to implement record-based log shipping using this
> alternative method, though this requires custom development, and changes
> will still only become visible to hot standby queries after a full WAL
> file has been shipped.
> An external program can call the
> function (see <xref linkend="functions-admin"/>)
> to find out the file name and the exact byte offset within it of
> the current end of WAL. It can then access the WAL file directly
> and copy the data from the last known end of WAL through the current end
> over to the standby servers. With this approach, the window for data
> loss is the polling cycle time of the copying program, which can be very
> small, and there is no wasted bandwidth from forcing partially-used
> segment files to be archived. Note that the standby servers'
> <varname>restore_command</varname> scripts can only deal with whole WAL
> so the incrementally copied data is not ordinarily made available to
> the standby servers. It is of use only when the primary dies —
> then the last partial WAL file is fed to the standby before allowing
> it to come up. The correct implementation of this process requires
> cooperation of the <varname>restore_command</varname> script with the
> copying program.
> Starting with <productname>PostgreSQL</productname> version 9.0, you can
> streaming replication (see <xref linkend="streaming-replication"/>) to
> achieve the same benefits with less effort.
> I think we should remove this whole section. Writing your own record-level
> log shipping by polling pg_walfile_name_offset() is malpractice on modern
> versions, when you could use streaming replication instead. The whole
> "Alternative Method for Log Shipping" section is pretty outdated.
> As of <productname>PostgreSQL</productname> 8.4,
> <function>amvacuumcleanup</function> will also be called at completion of
> <command>ANALYZE</command> operation. In this case
> <literal>stats</literal> is always
> NULL and any return value will be ignored. This case can be
> by checking <literal>info->analyze_only</literal>. It is recommended
> that the access method do nothing except post-insert cleanup in such a
> call, and that only in an autovacuum worker process.
> Let's remove the "As of PostgreSQL 8.4".
> The standard installation provides all the header files needed for
> application development as well as for server-side program
> development, such as custom functions or data types written in C.
> (Prior to <productname>PostgreSQL</productname> 8.0, a separate
> install-all-headers</literal> command was needed for the latter, but
> step has been folded into the standard install.)
> Interrogates the frontend/backend protocol being used.
> int PQprotocolVersion(const PGconn *conn);
> Applications might wish to use this function to determine whether
> features are supported. Currently, the possible values are 2 (2.0
> protocol), 3 (3.0 protocol), or zero (connection bad). The
> protocol version will
> not change after connection startup is complete, but it could
> theoretically change during a connection reset. The 3.0 protocol
> will normally be used when communicating with
> <productname>PostgreSQL</productname> 7.4 or later servers; pre-7.4
> support only protocol 2.0. (Protocol 1.0 is obsolete and not
> supported by <application>libpq</application>.)
> Talking about old versions, even very old ones, seems appropriate for a
> function like PQprotocolVersion().
Agreed, at least until we rip out the 2.0 protocol..
> libpq.sgml, on PQlibVersion():
> This function appeared in <productname>PostgreSQL</productname>
> version 9.1, so
> it cannot be used to detect required functionality in earlier
> versions, since calling it will create a link dependency
> on version 9.1 or later.
> Seems appropriate to keep.
+0 to remove, for my part. People building against libraries should
realize that they're creating a link dependency on things they're
> <xref linkend="libpq-PQinitSSL"/> has been present since
> <productname>PostgreSQL</productname> 8.0, while <xref
> was added in <productname>PostgreSQL</productname> 8.4, so <xref
> might be preferable for applications that need to work with older
> versions of <application>libpq</application>.
+1 to just remove PQinitSSL.
> The function
> Oid lo_creat(PGconn *conn, int mode);
> creates a new large object.
> The return value is the OID that was assigned to the new large object,
> or <symbol>InvalidOid</symbol> (zero) on failure.
> <replaceable class="parameter">mode</replaceable> is unused and
> ignored as of <productname>PostgreSQL</productname> 8.1; however, for
> backward compatibility with earlier releases it is best to
> set it to <symbol>INV_READ</symbol>, <symbol>INV_WRITE</symbol>,
> or <symbol>INV_READ</symbol> <literal>|</literal>
> (These symbolic constants are defined
> in the header file <filename>libpq/libpq-fs.h</filename>.)
> We need to say something about 'mode'. Keep.
We should drop that parameter and get rid of this.
> The interface was changed in version 8.4, to reflect the new FSM
> implementation introduced in the same version.
> <application>pg_standby</application> is designed to work with
> <productname>PostgreSQL</productname> 8.2 and later.
> IMHO we should remove pg_standby altogether. Until we get around to that, I
> think we should keep that note because it gives you a hint that it's old
+1 to remove pg_standby
> <application>pg_archivecleanup</application> is designed to work with
> <productname>PostgreSQL</productname> 8.0 and later when used as a
> standalone utility,
> or with <productname>PostgreSQL</productname> 9.0 and later when used as
> archive cleanup command.
+1 to remove pg_archivecleanup
> The examples shown below use tables in the
> regression test database.
> The outputs shown are taken from version 8.3.
> The behavior of earlier (or later) versions might vary.
> Should refresh the outputs..
> When used with a
> <literal>BEGIN</literal> block, <literal>EXIT</literal> passes
> control to the next statement after the end of the block.
> Note that a label must be used for this purpose; an unlabeled
> <literal>EXIT</literal> is never considered to match a
> <literal>BEGIN</literal> block. (This is a change from
> pre-8.4 releases of <productname>PostgreSQL</productname>, which
> would allow an unlabeled <literal>EXIT</literal> to match
> a <literal>BEGIN</literal> block.)
> Maybe keep for a couple more years.
+1 to remove
> This document describes version 3.0 of the protocol, implemented in
> <productname>PostgreSQL</productname> 7.4 and later. For descriptions
> of the earlier protocol versions, see previous releases of the
> <productname>PostgreSQL</productname> documentation. A single server
> can support multiple protocol versions. The initial startup-request
> message tells the server which protocol version the client is attempting
> use. If the major version requested by the client is not supported by
> the server, the connection will be rejected (for example, this would occur
> if the client requested protocol version 4.0, which does not exist as of
> this writing). If the minor version requested by the client is not
> supported by the server (e.g., the client requests version 3.1, but the
> server supports only 3.0), the server may either reject the connection or
> may respond with a NegotiateProtocolVersion message containing the highest
> minor protocol version which it supports. The client may then choose
> to continue with the connection using the specified protocol version or
> to abort the connection.
+1 to keep.
> This response is only possible for local Unix-domain connections
> on platforms that support SCM credential messages. The frontend
> must issue an SCM credential message and then send a single data
> byte. (The contents of the data byte are uninteresting; it's
> only used to ensure that the server waits long enough to receive
> the credential message.) If the credential is acceptable,
> the server responds with an
> AuthenticationOk, otherwise it responds with an ErrorResponse.
> (This message type is only issued by pre-9.1 servers. It may
> eventually be removed from the protocol specification.)
> Keep. It's surely still referred to in client libraries.
I'd rather have something like:
Only issued by pre-9.1 servers, no longer used. See older documentation
Or something along those lines.
> Data of a particular data type might be transmitted in any of several
> different <firstterm>formats</firstterm>. As of
> <productname>PostgreSQL</productname> 7.4
> the only supported formats are <quote>text</quote> and
> but the protocol makes provision for future extensions. The desired
> format for any value is specified by a <firstterm>format
> Clients can specify a format code for each transmitted parameter value
> and for each column of a query result. Text has format code zero,
> binary has format code one, and all other format codes are reserved
> for future definition.
> Could replace the "as of PostgreSQL 7.4" with "Currently", but it's not much
Seems a bit confusing to say "several different formats" and then say
"well, really only text and binary". How about:
Data of a particular data type may be transmitted in either
<quote>text</quote> or <quote>binary</quote> format. The desired format
for any value is specified by a <firstterm>format code</firstterm>.
Clients can specify a format code for each transmitted parameter
value and for each column of a query result. Text has format code zero,
binary has format code one, and all other format codes are reserved for
(Do we also point out that not everything supports binary..? If not,
seems like we should, but maybe that's covered)
> For a <command>COPY</command> command, the tag is
> <literal>COPY <replaceable>rows</replaceable></literal> where
> <replaceable>rows</replaceable> is the number of rows copied.
> (Note: the row count appears only in
> <productname>PostgreSQL</productname> 8.2 and later.)
> I think we should keep, since we mentioned earlier that the protocol
> documentation is for 7.4 and later.
+0 to remove. Someone working with a 8.1 or older server could look at
> alter_opfamily.sgml and create_opclass.sgml:
> Before <productname>PostgreSQL</productname> 8.4, the
> clause could include a <literal>RECHECK</literal> option. This is no
> supported because whether an index operator is <quote>lossy</quote> is
> determined on-the-fly at run time. This allows efficient handling of
> cases where an operator might or might not be lossy.
> Keep, since the syntax is still supported (but ignored).
We should remove the syntax. Having things that are accepted but
ignored isn't good, imv.
> The syntax
> CLUSTER <replaceable class="parameter">index_name</replaceable> ON
> <replaceable class="parameter">table_name</replaceable>
> is also supported for compatibility with pre-8.3
> Keep, since the syntax is still supported.
We should remove the syntax, or just document it as alternative syntax.
> The following syntax was used before
> version 9.0 and is still supported:
> The following syntax was used before
> version 7.3 and is still supported:
> Keep, since the syntax is still supported.
+0 to keep these references to when they were introduced.
> Before <productname>PostgreSQL</productname> version 8.3, the
> <literal>SET</literal> clause was not available, and so older functions
> contain rather complicated logic to save, set, and restore
> <varname>search_path</varname>. The <literal>SET</literal> clause is
> far easier
> to use for this purpose.
> Keep, those old functions with complicated might still exist in the wild.
> Before <productname>PostgreSQL</productname> version 8.3, the name of
> a generated array type was always exactly the element type's name with
> underscore character (<literal>_</literal>) prepended. (Type names were
> therefore restricted in length to one less character than other names.)
> While this is still usually the case, the array type name may vary from
> this in case of maximum-length names or collisions with user type names
> that begin with underscore. Writing code that depends on this convention
> is therefore deprecated. Instead, use
> <structname>pg_type</structname>.<structfield>typarray</structfield> to
> locate the array type
> associated with a given type.
> Let's keep it. We could remove the reference to 8.3, but would still need to
> explain the behaviour, and I think it's easiest to explain through its
> Before <productname>PostgreSQL</productname> version 8.2, the shell-type
> creation syntax
> <literal>CREATE TYPE <replaceable>name</replaceable></literal> did not
> The way to create a new base type was to create its input function first.
> In this approach, <productname>PostgreSQL</productname> will first see
> the name of the new data type as the return type of the input function.
> The shell type is implicitly created in this situation, and then it
> can be referenced in the definitions of the remaining I/O functions.
> This approach still works, but is deprecated and might be disallowed in
> some future release. Also, to avoid accidentally cluttering
> the catalogs with shell types as a result of simple typos in function
> definitions, a shell type will only be made this way when the input
> function is written in C.
> The deprecated way still works, so keep.
Bleh, I disagree, +1 to remove. We shouldn't be documenting how not to
do things in modern versions, just because that's how some old version
required it to be done.
> Since <productname>PostgreSQL</productname> 8.1, the concepts of users
> groups have been unified into a single kind of entity called a role.
> It is therefore no longer necessary to use the keyword
> to identify whether a grantee is a user or a group.
> is still allowed in the command, but it is a noise word.
> The GROUP keyword is still accepted, so let's keep it.
=1 to remove the GROUP keyword as being accepted here.
> The options <option>--docdir</option>, <option>--pkgincludedir</option>,
> <option>--localedir</option>, <option>--mandir</option>,
> <option>--sharedir</option>, <option>--sysconfdir</option>,
> <option>--cc</option>, <option>--cppflags</option>,
> <option>--cflags</option>, <option>--cflags_sl</option>,
> <option>--ldflags</option>, <option>--ldflags_sl</option>,
> and <option>--libs</option> were added in
> <productname>PostgreSQL</productname> 8.1.
> The option <option>--htmldir</option> was added in
> <productname>PostgreSQL</productname> 8.4.
> The option <option>--ldflags_ex</option> was added in
> <productname>PostgreSQL</productname> 9.0.
> Let's keep these. This could still be relevant if someone is maintaining an
> extension that's backwards compatible to old versions.
+0 to keep.
> Do not wait forever to acquire shared table locks at the beginning
> the dump. Instead, fail if unable to lock a table within the
> <replaceable class="parameter">timeout</replaceable>. The timeout
> may be
> specified in any of the formats accepted by <command>SET
> statement_timeout</command>. Allowed values vary depending on the
> version you are dumping from, but an integer number of milliseconds
> is accepted by all versions since 7.3. This option is ignored when
> dumping from a pre-7.3 server.
> pg_dump no longer supports pre-8.0 versions, so this is definitely obsolete.
> Before <productname>PostgreSQL</productname> 8.4,
> <application>psql</application> allowed the
> first argument of a single-letter backslash command to start
> directly after the command, without intervening whitespace.
> Now, some whitespace is required.
> Keep for a few more years.
+0 to remove.
> <para><literal>old-ascii</literal> style uses plain
> characters, using the formatting style used
> in <productname>PostgreSQL</productname> 8.4 and earlier.
> Newlines in data are shown using a <literal>:</literal>
> symbol in place of the left-hand column separator.
> When the data is wrapped from one line
> to the next without a newline character, a <literal>;</literal>
> symbol is used in place of the left-hand column separator.
> Keep, as long as we keep the format.
+1 to drop the format
> Before <productname>PostgreSQL</productname> 8.2, the
> <literal>.*</literal> syntax was not expanded in row constructors, so
> that writing <literal>ROW(t.*, 42)</literal> created a two-field row
> whose first
> field was another row value. The new behavior is usually more useful.
> If you need the old behavior of nested row values, write the inner
> row value without <literal>.*</literal>, for instance
> <literal>ROW(t, 42)</literal>.
> I'm inclined to keep this, someone might still need that behaviour, not
> necessary for backwards-compatibility but because you might want to do that
> in an application. Or rewrite without the reference to 8.2.
I'd suggest rewriting to discuss the options and move away from it being
a history lesson.
> For comparison, the <productname>PostgreSQL</productname> 8.1
> contained 10,441 unique words, a total of 335,420 words, and the most
> frequent word <quote>postgresql</quote> was mentioned 6,127 times in 655
> <!-- TODO we need to put a date on these numbers? -->
> Another example — the <productname>PostgreSQL</productname> mailing
> list archives contained 910,989 unique words with 57,491,343 lexemes in
> 461,020 messages.
> Refresh the numbers.
> In the SQL standard, there is a clear distinction between users and
> and users do not automatically inherit privileges while roles do. This
> behavior can be obtained in <productname>PostgreSQL</productname> by
> roles being used as SQL roles the <literal>INHERIT</literal> attribute,
> giving roles being used as SQL users the <literal>NOINHERIT</literal>
> However, <productname>PostgreSQL</productname> defaults to giving all
> the <literal>INHERIT</literal> attribute, for backward compatibility
> with pre-8.1
> releases in which users always had use of permissions granted to groups
> they were members of.
> Keep, since that's still how it behaves.
I'd just say that then:
<productname>PostgreSQL</productname> defaults to giving all roles the
<literal>INHERIT</literal> attribute, as this is generally seen as more
> Prior to <productname>PostgreSQL</productname> 8.3, there was no concept
> of operator families, and so any cross-data-type operators intended to
> used with an index had to be bound directly into the index's operator
> class. While this approach still works, it is deprecated because it
> makes an index's dependencies too broad, and because the planner can
> handle cross-data-type comparisons more effectively when both data types
> have operators in the same operator family.
> Keep, because the old method still works.
+1 to remove.
(Didn't look at the actual patch, I'm sure it does what you had said
|Next Message||John Naylor||2020-10-24 13:23:56||Re: Move catalog toast table and index declarations|
|Previous Message||Simon Riggs||2020-10-24 09:55:13||Re: Deleting older versions in unique indexes to avoid page splits|