On Fri, Feb 21, 2025 at 01:42:09PM +0100, Laurenz Albe wrote:
> On Fri, 2025-02-21 at 07:00 -0500, Bruce Momjian wrote:
> > > > diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
> > > > index 52b5b8f793b..705ca682777 100644
> > > > --- a/doc/src/s
On Fri, Feb 21, 2025 at 08:25:56AM +0100, Laurenz Albe wrote:
> On Thu, 2025-02-20 at 11:38 -0500, Bruce Momjian wrote:
> > On Tue, Feb 11, 2025 at 02:00:10PM +, PG Doc comments form wrote:
> > > Page: https://www.postgresql.org/docs/17/checksums.html
> > >
&
x27;s recommended to
> enable Checksums when initializing a cluster using initdb".
I can see your point. Attached is a doc patch that improves it. I
chose very simple language and plan to backpatch this to all supported
versions.
--
Bruce Momjian https://momjian.us
EDB
ng and manipulation of PL/pgSQL code.
I doubt it since no one has ever asked for this before, and we usually
tell them to look at the plpgsql parser if they want those details.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
On Thu, Oct 31, 2024 at 06:52:34PM -0400, Bruce Momjian wrote:
> On Fri, Nov 1, 2024 at 09:07:38AM +1100, Peter Smith wrote:
> > On Fri, Nov 1, 2024 at 2:16 AM Bruce Momjian wrote:
> > >
> > > On Fri, Oct 25, 2024 at 11:48:16PM +0200, Koen De Groote wrote:
> >
4) and zstd (if PostgreSQL was compiled with --with-zstd). The
> default value is off. The value on is synonym of pglz.”
I think we kept 'on' just for backward compatibility, so we don't
mention it in the docs anymore.
--
Bruce Momjian https://momjian.us
EDB
On Fri, Nov 1, 2024 at 10:23:25AM -0400, Bruce Momjian wrote:
> On Fri, Nov 1, 2024 at 11:04:53AM +, PG Doc comments form wrote:
> > The following documentation comment has been logged on the website:
> >
> > Page: https://www.postgresql.org/docs/16/ddl-rowsecurity
en made? I still see "#":
https://www.postgresql.org/docs/devel/tutorial-arch.html
I am actually fine with "#" since that is the symbol that will be added
to the URL.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
When a patient asks the doctor, "Am I going to die?", he means
"Am I going to die soon?"
't know
how to test if they are working properly or not. I assume ASCII double
quotes do work.
I am thinking Tatsuo's idea of using iconv to check files with any
non-ASCII characters is a better approach and will reply to that thread.
--
Bruce Momjian https://momjian.us
EDB
On Thu, Oct 31, 2024 at 03:24:06PM -0400, Bruce Momjian wrote:
> On Mon, Oct 21, 2024 at 02:01:37AM +, PG Doc comments form wrote:
> > The following documentation comment has been logged on the website:
> >
> > Page: https://www.postgresql.org/docs/17/bug-reporting
On Wed, Sep 27, 2023 at 07:23:09PM -0400, Bruce Momjian wrote:
> On Wed, Mar 1, 2023 at 09:45:00AM -0700, David G. Johnston wrote:
> > That may be, but the descriptive text and point of the example (which isn't
> > atomicity, but concurrency) doesn't even require the seco
On Wed, Sep 27, 2023 at 07:42:42PM -0400, Bruce Momjian wrote:
> On Tue, Feb 21, 2023 at 08:56:50AM -0700, David G. Johnston wrote:
> > On Tue, Feb 21, 2023 at 8:35 AM PG Doc comments form
> >
> > wrote:
> >
> > The following documentation comme
On Mon, Oct 14, 2024 at 07:21:32PM -0400, Bruce Momjian wrote:
> On Mon, Oct 14, 2024 at 07:15:50PM -0400, Bruce Momjian wrote:
> > On Wed, Sep 11, 2024 at 11:26:50PM +, PG Doc comments form wrote:
> > Yes, very good points. I have developed the attached patch which I
> &g
On Wed, Oct 16, 2024 at 05:11:54PM -0400, Bruce Momjian wrote:
> > Actually, there *is* a bug in the description, because experimentation
> > shows that CREATE DOMAIN accepts NULL in this syntax (as advertised)
> > but ALTER DOMAIN does not. We could alternatively decide that
db5ff434c9c3
> >
> > Is it worth going into that detail in the docs?
>
> Yes definitely. This not being properly documented caused me hours of work…
Patch applied, thanks.
--
Bruce Momjian https://momjian.us
EDB https://enterp
On Wed, Oct 16, 2024 at 09:36:00PM -0400, Bruce Momjian wrote:
> On Mon, May 6, 2024 at 04:15:24PM +0200, Laurenz Albe wrote:
> > On Sun, 2024-05-05 at 20:25 +, PG Doc comments form wrote:
> > > On this page:
> > > https://www.postgresql.org/docs/14/server-s
s "this is". May be better "The default behaviour is
> similar..."
I see your point. Attached is a patch which clarifies this.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
When a patient asks the doctor, &q
tement length that
> PostgreSQL can handle
> in the Appendix K. PostgreSQL Limits.
> If I'm not wrong it is 2147483648 that is a quite large number, larger than
> many other RDBMS.
Uh, we can add it, but we try to only list limits that are likely to be
exceeded.
--
Bruce Momjia
On Fri, Nov 1, 2024 at 09:07:38AM +1100, Peter Smith wrote:
> On Fri, Nov 1, 2024 at 2:16 AM Bruce Momjian wrote:
> >
> > On Fri, Oct 25, 2024 at 11:48:16PM +0200, Koen De Groote wrote:
> > > Number 2 would be perfect, I think. It leaves no doubt at all.
> >
&g
d is to fill in the bug
> report web-form available at the project's web site.", where "web site" is a
> link: https://www.postgresql.org/
>
> Suggestion: it should be a link to the web form (
> https://www.postgresql.org/account/submitbug/ )
Good idea, patch
On Fri, Oct 25, 2024 at 11:48:16PM +0200, Koen De Groote wrote:
> Number 2 would be perfect, I think. It leaves no doubt at all.
I went with even more direct wording, patch attached. Glad we could
improve this together --- the feedback from everyone was helpful.
--
Bruce Momj
rify that.
>
> It's the reason I created this mail: I would like it stated explicitly that
> the
> database process takes care of this for us.
Well, you are the first person to report this confusion, and we can't go
around explaining what Postgres does and does not do in each
had me confused early on, wondering if I had to perform the
> copy once the snapshot was ready.
Updated patch attached. I tried to tighten up the wording and add more
detail. I didn't see the point in repeating the same paragraph later on
so I removed it.
--
Bruce Momjian h
>
> Perhaps it should say:
>
> A common mistake is to forget to configure "listen_addresses" so that the
> server accepts remote TCP connections.
>
> Then "listen_addresses" could hyperlink to the parameter's documentation.
Agreed, patch attached.
--
itself.
>
> Am I missing something extremely simple, or can the description of the
> involved operations be made more consistent across documentation pages?
Is the attached patch an improvement?
--
Bruce Momjian https://momjian.us
EDB h
visibility: hidden;
> + text-decoration: none;
> +}
> +
> +a.id_link:hover:after {
> + content: "Pemalink to this heading";
> + font-size: 10px;
> + font-weight: normal;
> + text-decoration: none;
> + border: 1px solid #44;
>
at it
> is helpful to show this pattern as well. So if I were to do something
> about that, I would suggest the attached.
Do we want to apply this patch? I added a comma to the text, attached.
--
Bruce Momjian https://momjian.us
EDB https://
;
> [ CONSTRAINT constraint_name ]
> { NOT NULL | CHECK (expression) }
>
> to the ALTER DOMAIN page, and then remove the claim that it's
> identical to CREATE DOMAIN.
I have written the attached patch to document this. I assume this
should be backpatched to PG 12.
On Mon, Aug 19, 2024 at 05:42:33PM -0700, David G. Johnston wrote:
> On Mon, Aug 19, 2024 at 5:06 PM Bruce Momjian wrote:
> Well, it is more complicated than checking just HOME because it calls
> getpwuid_r() if HOME is not set:
>
> https://doxygen.po
On Mon, Oct 14, 2024 at 07:15:50PM -0400, Bruce Momjian wrote:
> On Wed, Sep 11, 2024 at 11:26:50PM +, PG Doc comments form wrote:
> > The following documentation comment has been logged on the website:
> >
> > Page: https://www.postgresql.org/docs/16/manag
example to
> the one that is currently shown.
Yes, very good points. I have developed the attached patch which I
think achieves the goals you mentioned. I plan to apply the patch for
master/PG 18.
I also removed the unnecessary mention of PG 9.1.
Seems the reply email address is g***@gm
ol".
>
> This is confusing, and I am also sometimes confused in the way you described
> above.
>
> I think the mess is too well established to be really cleaned up. But adding
> some clarity is a good thing, so +1.
I don't think our current setup is sustainable so I
s avoids putting redundant entries into the generated
postgresql.conf file.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
When a patient asks the doctor, "Am I going to die?", he means
"Am I going to die soon?"
ct_8c.html#a3f49cbb20595c1765bd0db5ff434c9c3
Is it worth going into that detail in the docs?
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
u?
https://momjian.us/main/blogs/pgblog/2020.html#July_17_2020
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
"To create a new database from the command line, in this example named
> mydb, you use the following command:"
Yes, good idea, patch applied to master, so it will appear in PG 18.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
criber is
> the
> - initial data copy. It does only the synchronization phase, which ensures
> - each table is brought up to a synchronized state.
> + replication setup and pg_createsubscriber is
> how
> + the data synchronization is done.
> pg_createsubscriber
> + does
arameters: username = 'nosuchuser'
Wow, this error goes all the way back to Postgres 12, which is our
earliest supported release. I have patched all our supported releases
with this fix. Thanks.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
Seems this needs improvement.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
e PostgreSQL term would be "attribute". Perhaps we should use that.
> Alternatively, what about "column value"? It is perhaps not accurate,
> because a Datum need not be stored in a column, but it might be readily
> understandable.
/current/app-psql.html
> >
> >
> > Nice catch, will fix.
>
> Committed, turns out the stray comma has been there since 7.3, so backpatched
> it all the way. Thanks for the report!
Yikes! :-)
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
in the attached patch, applied back to PG 16 where this typo
was created. Thanks for the report.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
diff --git a/doc/src/sgml/ref/create_
On Tue, Mar 26, 2024 at 11:07:07AM -0400, Bruce Momjian wrote:
> On Wed, Mar 6, 2024 at 12:42:09AM -0500, Tom Lane wrote:
> > I'm kind of inclined to not document this weirdness. I especially
> > don't think it's worth giving an example that neither explains
.
I retract my doc patch for this.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
sing the word "the"
> as shown below ..
> "Such transaction commits may never be completed if any one of THE
> synchronous standbys should crash."
Agreed, word "the" added to all supported versions.
--
Bruce Momjian https://momjian.us
EDB
r than 0-indexed.
Sure, updated patch attached.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index e5fa82c161..f9817
rvers/14.10?topic=smf-substr-function
Oracle doesn't have substring(), just substr(), and matches Informix
behavior, I think.
I have developed the attached doc patch to document this. The only
question is whether this substring behavior is so odd that we should not
document it.
--
Br
in the PG 16 minor release which will be
packaged on Monday.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
On Sun, Jan 28, 2024 at 10:11:18AM -0700, David G. Johnston wrote:
> On Fri, Jan 26, 2024 at 5:18 PM Bruce Momjian wrote:
>
> + Role membership with the inherit attribute can automatically use
> + whatever database privileges have been granted to all roles it
&
fferent way. Patch attached.
I also found we didn't document that GRANT can be used to modify a
membership's attributes even after it is created; I added that.
Just a reminder, this is for PG 16 and master.
--
Bruce Momjian https://momjian.us
EDB
On Wed, Jan 17, 2024 at 09:28:38AM +0100, Laurenz Albe wrote:
> On Tue, 2024-01-16 at 17:03 -0500, Bruce Momjian wrote:
> > I am unhappy with the documentation adjustments made to CREATE ROLE in
> > Postgres 16 by this commit:
> >
> > commit e3ce2de09d
> >
e-add this information, and clarify it. I
would like to apply this to PG 16 and master.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
test_inh.sh
Description: Bourne shell script
te
On Wed, Jan 10, 2024 at 06:05:17PM +0100, Álvaro Herrera wrote:
> On 2024-Jan-10, Bruce Momjian wrote:
>
> > On Mon, Jan 8, 2024 at 04:50:19PM -0500, Tom Lane wrote:
> > > Bruce Momjian writes:
> > > > Agreed, updated patch attached.
> > >
> > &g
On Mon, Jan 8, 2024 at 04:50:19PM -0500, Tom Lane wrote:
> Bruce Momjian writes:
> > Agreed, updated patch attached.
>
> WFM.
Patch applied back to PG 16, which is where the erroneous text was
added.
--
Bruce Momjian https://m
b anyway.
>
> Or if you want a few more words, "name of the operating-system user
> running initdb". I don't like "installation user", that's just about
> as vague as could be.
Agreed, updated patch attached.
--
Bruce Momjian https://momji
On Sat, Jan 6, 2024 at 08:11:14PM -0700, David G. Johnston wrote:
> On Saturday, January 6, 2024, Bruce Momjian wrote:
>
> This commit:
>
> commit 910cab820d
> Author: Alvaro Herrera
> Date: Fri Nov 18 11:59:26 2022 +0100
>
cluster owner.
This seems wrong since the cluster owner doesn't exist until the cluster
is created. The text exists in PG 16 and master. The attached patch
fixes this.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Onl
On Thu, Dec 7, 2023 at 02:18:28PM -0500, Bruce Momjian wrote:
> Yes, there were a few problems with my initial patch. First, I should
> have used "Z" instead of a Z which could be interpreted as a format
> specification; I had already done that for "T" in the exampl
d for some time.
...
I have CC'ed the patch author.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
On Sun, Nov 26, 2023 at 08:59:02PM +0100, Laurenz Albe wrote:
> On Fri, 2023-11-24 at 13:14 -0500, Bruce Momjian wrote:
> > On Thu, Nov 23, 2023 at 08:36:34AM +0100, Laurenz Albe wrote:
> > > On Wed, 2023-11-22 at 14:49 -0800, Peter Geoghegan wrote:
> > > > I don'
On Mon, Nov 20, 2023 at 08:20:57PM -0700, David G. Johnston wrote:
> On Mon, Nov 20, 2023 at 8:16 PM Bruce Momjian wrote:
>
> On Mon, Nov 20, 2023 at 07:19:39PM -0700, David G. Johnston wrote:
> > The placement in the numbered listing section feels wrong, I am OK with
>
On Wed, Nov 22, 2023 at 10:19:57AM +0100, Laurenz Albe wrote:
> On Tue, 2023-11-21 at 22:27 -0500, Bruce Momjian wrote:
> > I like this six year old patch so would like to apply it to master,
> > attached.
>
> +1, since it is arguably a bug fix.
Patch applied to master.
y to get the time zone _name_ or even the offset from the AT TIME ZONE
value, so we must just pass the literal "Z" from the input to the output.
This proves Alvaro's point on this issue:
SELECT pg_typeof(current_timestamp AT TIME ZONE 'America/Santiago');
are of.
> I
> like "convert" slightly better instead.
Nine year old patch, but still valid, so applied to master.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
tgreSQL knowledge, like me.
I moved the parition pagagraph to a more logical location and tried to
clarify the new paragraph to be more targeted on the goal, patch
attached.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only
On Thu, Nov 23, 2023 at 09:29:39AM +0100, Laurenz Albe wrote:
> On Wed, 2023-11-22 at 11:58 -0500, Bruce Momjian wrote:
> > Okay, I moved it into the "Note" section that talked about ISO 8601
> > output with "T", in the attached patch.
>
> Fine by me, exc
:
>
> "This option may only be used on a populated materialized view."?
>
> Your clarification is much appreciated.
I know this is six years old, but fixed in master with the attached
patch.
--
Bruce Momjian https://momjian.us
EDB
ce those effects may
have contributed to the row being excluded from insertion.
I modified the attached patch to explain this since it is not really the
same as modifying the actual row. Does that add any value? If not,
let's remove it.
--
Bruce Momjian https://mo
r Examples".
I originally thought it belonged in section 9.8 too, but I think the
value of this example is ISO 8601 and I don't see how we can cleanly
mention that in table 9.31.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
gml around line 2552.
>
> +1 for moving it to section 8.5.2.
Okay, I moved it into the "Note" section that talked about ISO 8601
output with "T", in the attached patch.
I will apply this only to master since it is not a correction.
--
Bruce Momjian
developed the attached patch I would like to apply to master.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
inde
t;> reserved words.
> > Ouch. Shows you how old this module is :-(
>
> Indeed.
>
> >> I propose the attached patch to fix that.
> > Um, the attached file seems empty from here.
>
> Ooops, sorry. It is attached.
I like this six year old patch so would l
On Wed, Nov 22, 2023 at 03:25:07PM +1300, Thomas Munro wrote:
> On Wed, Nov 22, 2023 at 2:12 PM Bruce Momjian wrote:
> > On Sat, Aug 12, 2017 at 10:47:00PM +0100, John Ekins wrote:
> > > Sure. Camcontrol does indeed cover IDE, SCSI and SAS drives.
> > >
> > >
On Thu, Aug 31, 2017 at 09:22:22AM -0700, Peter Geoghegan wrote:
> On Thu, Aug 31, 2017 at 6:25 AM, Bruce Momjian wrote:
> > On Mon, Jul 3, 2017 at 08:07:10PM +, n...@fairwindsoft.com wrote:
> >> The following documentation comment has been logged on the website:
>
Support Enabled Value Vendor
> write cacheyes yes
>
> I appreciate the Postgresql docs are not meant to be FreeBSD tutorials.
I know this email is six years old, but I have applied this fix to all
supported Postgres versions. A huge apology
/sql-alterdefaultprivileges.html
We felt the doc rewrite was too extensive to backpatch.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
;FOR UPDATE" so I missed that
section; updated patch attached.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/selec
(i.e., an unaliased table name or an alias in the sibling FROM
> clause attached to this level of the query). I like this better anyway on the
> grounds that the thing being referenced can be a subquery or a view as well as
> a table.
Okay, how is the attached patch?
x | x
---+---
SELECT * FROM test AS t1 JOIN test AS t2 ON (TRUE) FOR UPDATE OF t2;
x | x
---+---
The attached patch documents this.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.co
link to the LIMIT
> section in the SELECT reference page. I also renamed the "number"
> variables to the same names used in the SELECT reference page and put
> OFFSET in a new line (it looks visually better).
I applied the attached patch based on your p
On Thu, Nov 2, 2023 at 06:22:59PM -0400, Bruce Momjian wrote:
> On Thu, Nov 2, 2023 at 03:42:53PM +0100, Laurenz Albe wrote:
> > On Thu, 2023-11-02 at 10:14 -0400, Bruce Momjian wrote:
> > > Better, though "Is the range's upper bound unbounded?" makes me cring
On Thu, Nov 2, 2023 at 11:08:53AM -0400, Bruce Momjian wrote:
> On Thu, Nov 2, 2023 at 09:58:54AM -0400, Tom Lane wrote:
> > Bruce Momjian writes:
> > > I found a cleaner improvement, attached.
> >
> > OK by me. Maybe that doesn't make the point strong
is this correction accurate? It seems so to me.
After flushing WAL the writer sleeps for the length of time given
by wal_writer_delay, unless woken up sooner
--> by an asynchronously committing transaction.
--
Bruce Momjian https://momjian.us
EDB
This patch is 4.5 years old, but still valid. Fixed with the attached
patch applied to master.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
diff --git a/doc/src/sgml/wal.sgml
On Thu, Nov 9, 2023 at 05:03:33PM -0500, Tom Lane wrote:
> Bruce Momjian writes:
> > On Tue, Jul 16, 2019 at 02:01:00AM +, PG Doc comments form wrote:
> >> I suppose it should be warned on the pages that foreign credentials with be
> >> stored as simple text and wi
know this is four years old, but the attached patch documents it. I
don't think postgresql-fdw needs it since it relies on user mapping and
discourages passwords in the connection string.
--
Bruce Momjian https://momjian.us
EDB https://e
his patch.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
t;
> parallel with non-DDL activity on the table.
I know this report is four years old, but attached patch applied to
master.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
On Sat, Oct 28, 2023 at 04:04:47PM -0400, Bruce Momjian wrote:
> On Tue, Aug 2, 2022 at 08:08:07PM +, PG Doc comments form wrote:
> > 21.1.1 Loading or Reloading the Configuration
> > The pg_hba.conf file is read on start-up...
> > Note: The preceding statement...
On Sat, Oct 28, 2023 at 03:14:32PM -0400, Bruce Momjian wrote:
> On Sat, Oct 28, 2023 at 02:42:06PM -0400, Tom Lane wrote:
> > Bruce Momjian writes:
> > > Sorry, I attached a _colorized_ diff; here is a normal one.
> >
> > The new sentence is fine in isolation, bu
ugh to be useful.
>
> I am not speaking about a warning at creation time, but rather a warning in
> the
> docs. Something like: Although a table with e.g. 1600 bigint columns can be
> created, creating a tuple of more than 8160 bytes will fail.
It is in the "limits" docs:
On Thu, Nov 2, 2023 at 09:51:58PM -0400, Bruce Momjian wrote:
> On Wed, Nov 1, 2023 at 09:31:52PM +0100, Laurenz Albe wrote:
> > There is another patch in the current commitfest that addresses a similar
> > problem, triggered by another complaint:
> > https://commitfest.p
On Wed, Nov 1, 2023 at 09:31:52PM +0100, Laurenz Albe wrote:
> On Wed, 2023-11-01 at 13:09 -0400, Bruce Momjian wrote:
> > On Thu, Feb 18, 2021 at 08:16:13AM +0100, Laurenz Albe wrote:
> > > On Wed, 2021-02-17 at 15:08 -0500, Jordi Gutiérrez Hermoso wrote:
> > > >
On Thu, Nov 2, 2023 at 03:42:53PM +0100, Laurenz Albe wrote:
> On Thu, 2023-11-02 at 10:14 -0400, Bruce Momjian wrote:
> > Better, though "Is the range's upper bound unbounded?" makes me cringe.
> >
> > Oh, yeah, totally cringe, me too. :-)
> >
> &
On Thu, Nov 2, 2023 at 09:58:54AM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > I found a cleaner improvement, attached.
>
> OK by me. Maybe that doesn't make the point strongly enough,
> but we can hope it's enough.
Agreed. I thought last night about the s
On Thu, Nov 2, 2023 at 08:56:13AM +0100, Laurenz Albe wrote:
> On Wed, 2023-11-01 at 18:03 -0400, Bruce Momjian wrote:
> > On Wed, Nov 1, 2023 at 09:40:43PM +0100, Laurenz Albe wrote:
> > > > Yes, I agree this documentation needs help.
> > > >
> > >
On Wed, Nov 1, 2023 at 07:34:59PM -0400, Bruce Momjian wrote:
> On Wed, Nov 1, 2023 at 07:12:48PM -0400, Tom Lane wrote:
> > Bruce Momjian writes:
> > > On Wed, Nov 1, 2023 at 06:32:37PM -0400, Tom Lane wrote:
> > >> But it *is* permissible, unless we add code to
On Wed, Nov 1, 2023 at 07:12:48PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > On Wed, Nov 1, 2023 at 06:32:37PM -0400, Tom Lane wrote:
> >> But it *is* permissible, unless we add code to reject it during
> >> SET as Bruce mentioned. Which seems fairly
On Wed, Nov 1, 2023 at 06:32:37PM -0400, Tom Lane wrote:
> "David G. Johnston" writes:
> > On Wednesday, November 1, 2023, Bruce Momjian wrote:
> >> Did you want an error from the SET command?
>
> > That would probably be a decent addition but the req
years old, but I am now looking at this email can
can't see the problem:
SET default_tablespace = 'pg_global';
CREATE TABLE test (x int);
ERROR: only shared relations can be placed in pg_global tablespace
Did you want an error from the SET command?
--
Bru
1 - 100 of 774 matches
Mail list logo
