On Thursday, May 23, 2024, Karki, Sanjay wrote:
>
> I need to grant select on privilege in pg_catalog to user so I can connect
> via Toad Data point ,
>
> Users can already select from the tables in pg_catalog, grant able
privileges not required or allowed. Of course, some specific data is
On Monday, May 20, 2024, jian he wrote:
> hi.
>
> https://www.postgresql.org/docs/current/functions-
> matching.html#FUNCTIONS-POSIX-REGEXP
>
>
> If there is a match,
> the source string is returned with the replacement string substituted
> for the matching substring.
>
This happens
On Fri, May 17, 2024 at 4:57 PM Erik Wienhold wrote:
> On 2024-05-16 17:47 +0200, David G. Johnston wrote:
> > On Wed, May 15, 2024 at 8:46 AM Robert Haas
> wrote:
> >
> > > On Thu, Apr 4, 2024 at 12:41 AM Erik Wienhold wrote:
> > > > Thanks, fixed in v
On Friday, May 17, 2024, Joe Conway wrote:
>
> I wrote:
>
>> Namely, the week before commitfest I don't actually know if I will have
>> the time during that month, but I will make sure my patch is in the
>> commitfest just in case I get a few clear days to work on it. Because if it
>> isn't
On Thu, May 16, 2024 at 4:11 PM Michael Paquier wrote:
> On Thu, May 16, 2024 at 11:57:10AM +0300, Aleksander Alekseev wrote:
> > I propose my original v1 patch for correcting the --help output of
> > 'postgres' too. I agree with the above comments that corresponding
> > changes in v4 became
On Thu, May 16, 2024 at 1:46 PM Melanie Plageman
wrote:
>
> I should probably simply
> withdraw and re-register them. My justification was that I'll lose
> them if I don't keep them in the commitfest app. But, I could just,
> you know, save them somewhere myself instead of polluting the
>
On Thu, May 16, 2024 at 11:30 AM Robert Haas wrote:
> Hi,
>
> The original intent of CommitFests, and of commitfest.postgresql.org
> by extension, was to provide a place where patches could be registered
> to indicate that they needed to be reviewed, thus enabling patch
> authors and patch
On Wed, May 15, 2024 at 8:46 AM Robert Haas wrote:
> On Thu, Apr 4, 2024 at 12:41 AM Erik Wienhold wrote:
> > Thanks, fixed in v4. Looks like American English prefers that comma and
> > it's also more common in our docs.
>
> Reviewing this patch:
>
> - Creates a typed table, which takes
On Wednesday, May 15, 2024, jian he wrote:
> On Thu, May 9, 2024 at 12:04 PM Bruce Momjian wrote:
> >
> > I have committed the first draft of the PG 17 release notes; you can
> > see the results here:
> >
> > https://momjian.us/pgsql_docs/release-17.html
> >
>
> in section: E.1.2.
On Wed, May 15, 2024 at 6:35 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
>
> If in core I would still want to expose this as say a contrib module
> binary instead of hacking it into postgres. It would be our first server
> program entry there.
>
>
Sorry fo
On Wed, May 15, 2024 at 1:00 PM Robert Haas wrote:
> On Wed, May 15, 2024 at 3:28 PM Tom Lane wrote:
> > Sorry: "make sense" was a poorly chosen phrase there. What I was
> > doubting, and continue to doubt, is that 100% checking of what
> > you can check without catalog access and 0% checking
On Wed, May 15, 2024 at 1:19 PM Robert Haas wrote:
>
> So my point was: to me, N is more self-documenting than replace_at,
> and less self-documenting than count or occurrence.
>
> If your mileage varies on that point, so be it!
>
>
Maybe just "match" instead of "replace_match".
Reading this it
On Wed, May 15, 2024 at 12:07 PM Robert Haas wrote:
> On Wed, May 15, 2024 at 3:01 PM David G. Johnston
> wrote:
> > I think this confusion goes to show that replacing N with count doesn't
> work.
> >
> > "replace_at" comes to mind as a better name.
> I
On Wed, May 15, 2024 at 12:52 PM Robert Haas wrote:
> On Wed, May 15, 2024 at 3:25 PM David G. Johnston
> wrote:
> > The function replaces matches, not random characters. And if you are
> reading the documentation I find it implausible that the wording I
> suggested would
On Wed, May 15, 2024 at 12:35 PM Josef Šimánek
wrote:
> st 15. 5. 2024 v 21:33 odesílatel David G. Johnston
> napsal:
>
> > Now, in my ideal world something like this could be made as an extension
> so that it can work on older versions and not have to be maintained by
> c
On Wed, May 15, 2024 at 12:18 PM wrote:
> Tom Lane:
> >> This is really what is missing for the ecosystem. A libpqparser for
> >> tools to use: Formatters, linters, query rewriters, simple syntax
> >> checkers... they are all missing access to postgres' own parser.
> >
> > To get to that, you'd
On Wed, May 15, 2024 at 12:07 PM Robert Haas wrote:
> On Wed, May 15, 2024 at 3:01 PM David G. Johnston
> wrote:
> > I think this confusion goes to show that replacing N with count doesn't
> work.
> >
> > "replace_at" comes to mind as a better name.
>
>
On Wed, May 15, 2024 at 11:46 AM Robert Haas wrote:
> On Thu, Apr 4, 2024 at 9:55 AM jian he
> wrote:
> > in the regexp_replace explanation section.
> > changing "N" to lower-case would be misleading for regexp_replace?
> > so I choose "count".
>
> I don't see why that would be confusing for
On Wed, May 15, 2024 at 2:49 AM Peter Eisentraut
wrote:
> On 15.05.24 04:07, Michael Paquier wrote:
> > Not sure that these additions in --help or the docs are necessary.
> > The rest looks OK.
> >
> > -"You must specify the --config-file or -D invocation "
> > +"You must specify the
On Tue, May 14, 2024 at 9:03 AM Robert Haas wrote:
> On Tue, Apr 16, 2024 at 3:06 AM Pavel Luzanov
> wrote:
> > As for the Login column and its values.
> > I'm not sure about using "Can" instead of "yes" to represent true.
> > In other psql commands, boolean values are always shown as yes/no.
>
On Saturday, May 11, 2024, Thom Brown wrote:
>
> Sat, May 11, 2024, 16:34 David G. Johnston
> wrote:
>
> My plan is to have a v4 out next week, without or without a review of this
>> draft, but then the subsequent few weeks will probably be a bit quiet.
>>
>
&g
On Fri, May 3, 2024 at 9:00 AM David G. Johnston
wrote:
> On Fri, May 3, 2024 at 8:44 AM Tom Lane wrote:
>
>> Having said that, I reiterate my proposal that we make it a new
>>
> under DDL, before 5.2 Default Values which is the first
>> place in ddl.sgml that assu
On Thu, May 9, 2024 at 1:16 PM Andres Freund wrote:
> Hi,
>
> On 2024-05-09 09:23:37 -0700, David G. Johnston wrote:
> > This needs updating:
> > https://www.postgresql.org/docs/current/docguide-build-meson.html
>
> You mean it should have a syntax target? Or that some
On Thu, May 9, 2024 at 12:12 PM Dagfinn Ilmari Mannsåker
wrote:
> "David G. Johnston" writes:
>
> > I've been using "ninja html" which isn't shown here.
>
> The /devel/ version has a link to the full list of doc targets:
>
>
> https://www.postg
$subject
Make has one:
https://www.postgresql.org/docs/current/docguide-build.html#DOCGUIDE-BUILD-SYNTAX-CHECK
This needs updating:
https://www.postgresql.org/docs/current/docguide-build-meson.html
I've been using "ninja html" which isn't shown here. Also, as a sanity
check, running that
On Thursday, May 9, 2024, Dave Cramer wrote:
> Greetings,
>
> The JDBC driver is currently keeping a per connection cache of types in
> the driver. We are seeing cases where the number of columns is quite high.
> In one case Prevent fetchFieldMetaData() from being run when unnecessary.
> · Issue
On Tue, May 7, 2024 at 7:54 AM Bruce Momjian wrote:
> In this commit:
>
> commit 34768ee3616
> Author: Peter Eisentraut
> Date: Sun Mar 24 07:37:13 2024 +0100
>
> Add temporal FOREIGN KEY contraints
>
> Add PERIOD clause to foreign key
On Monday, May 6, 2024, Peter Burbery wrote:
>
> Business Use-case: I want to create a table named things_that_take_up_a_
> lot_of_storage_and_space_on_a_computer_and_hard_drive of 75 characters. I
> also want to create a column named thing_that_takes_up_a_
>
On Friday, May 3, 2024, Peter Burbery wrote:
> Dear pgsql-hackers,
>
> One-line Summary:
> Proposal to introduce the CREATE OR REPLACE syntax for EVENT TRIGGER in
> PostgreSQL.
>
> Business Use-case:
> Currently, to modify an EVENT TRIGGER, one must drop and recreate it. This
> proposal aims to
On Fri, May 3, 2024 at 8:44 AM Tom Lane wrote:
> "David G. Johnston" writes:
> > On Fri, May 3, 2024 at 7:10 AM Peter Eisentraut
> > wrote:
> >> On 02.05.24 17:23, David G. Johnston wrote:
> >>> I chose to add a new sect1 in the user g
On Fri, May 3, 2024 at 7:10 AM Peter Eisentraut
wrote:
> On 02.05.24 17:23, David G. Johnston wrote:
> > Version 2 attached. Still a draft, focused on topic picking and overall
> > structure. Examples and links planned plus the usual semantic markup
> stuff.
> >
> &
On Fri, May 3, 2024 at 1:14 AM jian he wrote:
> On Fri, May 3, 2024 at 2:47 PM Laurenz Albe
> wrote:
> >
> > On Thu, 2024-05-02 at 08:23 -0700, David G. Johnston wrote:
> > > Version 2 attached. Still a draft, focused on topic picking and
> overall structu
One easily made because we assume if you are here you "know"
what data is, but there is still stuff to be discussed, if nothing else to
establish a common understanding between us and our users.
David J.
From 7798121992154edab4768d7eab5a89be04730b2f Mon Sep 17 00:00:00 2001
From: &qu
On Thu, May 2, 2024 at 6:17 AM jian he wrote:
> explain (verbose, verbose off, analyze on, analyze off, analyze on)
>
>
I would just update this paragraph to note the last one wins behavior.
"When the option list is surrounded by parentheses, the options can be
written in any order. However,
in its own file.
David J.
[1] https://www.postgresql.org/message-id/1859814.1714532025%40sss.pgh.pa.us
From a068247e92e620455a925a0ae746adc225ae1339 Mon Sep 17 00:00:00 2001
From: "David G. Johnston"
Date: Wed, 1 May 2024 07:45:48 -0700
Subject: [PATCH] Document NULL
---
doc/src/sgm
On Monday, April 29, 2024, Tom Lane wrote:
> "David G. Johnston" writes:
> > My solution to this was to rely on the fact that the bootstrap superuser
> is
> > assigned OID 10 regardless of its name.
>
> Yeah, I wrote it that way to start with too, but reconside
On Monday, April 29, 2024, Tom Lane wrote:
> Daniel Gustafsson writes:
> >> On 28 Apr 2024, at 20:52, Tom Lane wrote:
>
>
> >> This is of course not bulletproof: with a sufficiently weird
> >> bootstrap superuser name, we could get false matches to parts
> >> of "regress_dump_test_role" or to
On Sunday, April 28, 2024, Michael Paquier wrote:
> On Sun, Apr 28, 2024 at 06:45:30PM -0700, David G. Johnston wrote:
> > My preference would be to limit this section to a single example. The
> > numeric one, as it provides values for more output columns. I would
> cha
On Sunday, April 28, 2024, jian he wrote:
>
>
> after checking the definition of [1], [2],
> maybe here we should use
>
Possibly, though I’d be curious to see how consistent we are on this point
elsewhere before making a point of it.
>
> and also add `(1 row)` information.
Doesn’t seem
On Sunday, April 28, 2024, Alexander Lakhin wrote:
>
> When we deal with mixed ownership, say, bob is an owner of a
> partitioned table, but not an owner of a partition, should we
> allow him to perform merge with that partition?
>
>
Attaching via alter table requires the user to own both the
On Sunday, April 28, 2024, Alexander Lakhin wrote:
>
> When we deal with mixed ownership, say, bob is an owner of a
> partitioned table, but not an owner of a partition, should we
> allow him to perform merge with that partition?
>
>
IIUC Merge causes the source tables to be dropped, their data
On Sat, Apr 27, 2024 at 12:47 AM Sushrut Shivaswamy <
sushrut.shivasw...@gmail.com> wrote:
>
> I"m trying to read the rows of a table in chunks to process them in a
> background worker.
>
This list really isn't the place for this kind of discussion. You are
doing application-level stuff, not
On Sat, Apr 27, 2024 at 6:55 AM Imseih (AWS), Sami
wrote:
>
> Hmm, you raise a good point. Isn't this a fundamental problem
> with prepared statements? If there is DDL on the
> relations of the prepared statement query, shouldn't the prepared
> statement be considered invalid at that point and
On Wed, Apr 24, 2024 at 4:35 PM Michael Paquier wrote:
>
> I disagree here, actually. Temporary tables are a different beast
> because they require automated cleanup which would include interacting
> with the partitionining information if temp and non-temp relations are
> mixed. That's why the
On Wed, Apr 24, 2024 at 1:26 PM Nathan Bossart
wrote:
> On Wed, Apr 24, 2024 at 04:17:44PM +0900, Michael Paquier wrote:
> > - Support ALTER TABLE .. SET LOGGED/UNLOGGED for partitioned tables,
> > where the command only works on partitioned tables so that's only a
> > catalog switch.
>
> I'm
On Wed, Apr 24, 2024 at 7:45 AM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Wed, Apr 24, 2024 at 3:30 AM Peter Eisentraut
> wrote:
>
>> > + The reliability characteristics of a table are governed by its
>> > + persistence mode. The default
On Wed, Apr 24, 2024 at 3:30 AM Peter Eisentraut
wrote:
> > + The reliability characteristics of a table are governed by its
> > + persistence mode. The default mode is described
> > + here
> > + There are two alternative modes that can be specified during
> > + table creation:
>
Any thoughts?
On Thu, Jan 25, 2024 at 1:59 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> Hey,
>
> In a nearby user complaint email [1] some missing information regarding
> ownership reassignment came to light. I took that and went a bit further
> to add wh
Thoughts anyone?
On Thu, Feb 1, 2024 at 3:47 PM David G. Johnston
wrote:
> Motivated by a recent complaint [1] I found the hostssl related material
> in our docs quite verbose and even repetitive. Some of that is normal
> since we have both an overview/walk-through sectio
not so is
discovered by their omission when discussing those topics.
[1]
https://www.postgresql.org/message-id/flat/15954-b61523bed4b110c4%40postgresql.org
From e375044d55809d239be33f31c4efa8410790d3f0 Mon Sep 17 00:00:00 2001
From: "David G. Johnston"
Date: Mon, 22 Apr 2024 11:51:53 -070
On Sun, Feb 18, 2024 at 4:14 AM Pavel Luzanov
wrote:
> 2. Tom's advise:
>
> Not sure it's worth worrying about
>
> Show real values for 'Valid until' and 'Connection limit' without any hints.
>
>
At this point I'm on board with retaining the \dr charter of simply being
an easy way to access the
On Sat, Apr 13, 2024 at 7:02 PM Wen Yi wrote:
> I think we can change the output like this:
>
> postgres=# \du
> List of roles
> Role name | Login | Attributes | Password | Valid until | Connection
> limit
>
>
On Sun, Apr 14, 2024 at 7:03 PM David Rowley wrote:
> On Mon, 15 Apr 2024 at 13:37, David G. Johnston
> wrote:
> > Seems we can improve things by simply removing the "rule of thumb"
> sentence altogether. The prior paragraph states the things the queryid
> depends
On Sun, Apr 14, 2024 at 6:32 PM David Rowley wrote:
> On Mon, 15 Apr 2024 at 13:19, Tom Lane wrote:
> >
> > Michael Paquier writes:
> > > On Mon, Apr 15, 2024 at 11:20:16AM +1200, David Rowley wrote:
> > >> 1. We cannot change Node enums in minor versions
> > >> 2. We're *unlikely* to add
On Sun, Apr 14, 2024 at 4:20 PM David Rowley wrote:
>
> I've drafted a patch which I think improves things, but it probably
> needs more work and opinions.
>
>
Seems we can improve things by simply removing the "rule of thumb" sentence
altogether. The prior paragraph states the things the
On Saturday, April 13, 2024, Dmitry Koterov
wrote:
>
>
> % psql --version
> psql (PostgreSQL) 16.0
>
How did you install this and can you install other, supported, versions?
David J.
On Fri, Apr 5, 2024 at 9:18 AM Robert Haas wrote:
> On Fri, Apr 5, 2024 at 12:15 PM David G. Johnston
> wrote:
> > Here is a link to my attempt at this a couple of years ago. It
> basically "abuses" refentry.
> >
> >
> https://www.postgresql.org/m
On Fri, Apr 5, 2024 at 9:01 AM Robert Haas wrote:
>
> > The rendering can be adjusted to some degree, but then we also need to
> > make sure any new chunking makes sense in other chapters. (And it might
> > also change a bunch of externally known HTML links.)
>
> I looked into this and I'm
On Thu, Apr 4, 2024 at 11:23 AM Bruce Momjian wrote:
> On Wed, Apr 3, 2024 at 06:01:41PM -0700, David G. Johnston wrote:
> >
> > The PostgreSQL Global Development Group supports a major version for 5
> years
> > -after its initial release. After its five year annive
On Thu, Mar 28, 2024 at 8:02 PM Erik Wienhold wrote:
> Thanks, that sounds better. I incorporated that with some minor edits
> in the attached v3.
>
Looks good.
You added my missing ( but dropped the comma after "i.e."
diff --git a/doc/src/sgml/ref/create_table.sgml
On Tue, Apr 2, 2024 at 1:47 PM Bruce Momjian wrote:
> On Tue, Apr 2, 2024 at 11:34:46AM +0200, Magnus Hagander wrote:
>
> Okay, I changed "superseded" to "old", and changed "latest" to
> "current", patch attached.
>
>
I took a pass at this and found a few items of note. Changes on top of
On Thu, Mar 7, 2024 at 9:29 PM Erik Wienhold wrote:
> I wrote:
> > The attached v2 is a simpler patch that instead modifies the existing
> > error message.
>
> Forgot to attach v2.
>
>
For consideration for the doc portion. The existing wording is too
imprecise for my liking and just tacking on
On Wed, Mar 27, 2024 at 5:43 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
>
> This section is also the main entry point for users into the configuration
> subsystem and hasn't been updated to reflect this new feature. That seems
> like an oversight that nee
On Wed, Mar 27, 2024 at 5:17 PM Bruce Momjian wrote:
> On Thu, Mar 28, 2024 at 12:43:29AM +0100, Jelte Fennema-Nio wrote:
> > + xreflabel="allow_alter_system">
> > + allow_alter_system (boolean)
> > +
> > + allow_alter_system configuration
> parameter
> > +
> > +
On Wed, Mar 27, 2024 at 3:18 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Wed, Mar 27, 2024 at 3:13 PM Bruce Momjian wrote:
>
>> On Wed, Mar 27, 2024 at 06:09:02PM -0400, Bruce Momjian wrote:
>> > On Wed, Mar 27, 2024 at 11:05:55AM -0400, Robert Haa
On Wed, Mar 27, 2024 at 3:13 PM Bruce Momjian wrote:
> On Wed, Mar 27, 2024 at 06:09:02PM -0400, Bruce Momjian wrote:
> > On Wed, Mar 27, 2024 at 11:05:55AM -0400, Robert Haas wrote:
> > > On Wed, Mar 27, 2024 at 10:43 AM Jelte Fennema-Nio
> wrote:
> > > > Alright, changed the GUC name to
On Wed, Mar 27, 2024 at 10:12 AM Isaac Morland
wrote:
> On Wed, 27 Mar 2024 at 13:05, Greg Sabino Mullane
> wrote:
>
>> The purpose of the setting is to prevent accidental
>>> modifications via ALTER SYSTEM in environments where
>>
>>
>> The emphasis on 'accidental' seems a bit heavy here, and
On Sun, Mar 24, 2024 at 5:49 AM ShadowGhost
wrote:
> Cast_jsonb_to_hstore WIP
> v1
> This extension add function that can cast jsonb to hstore.
> That link to my github where does my extension lie
> https://github.com/antuanviolin/cast_jsonb_to_hstore
>
If you are intending to submit this to
On Fri, Mar 22, 2024 at 11:19 AM Robert Haas wrote:
> On Fri, Mar 22, 2024 at 1:35 PM Bruce Momjian wrote:
>
> But that all seems like a separate question from why we have the
> statistic collector views in a completely different part of the
> documentation from the rest of the system views. My
On Fri, Mar 22, 2024, 09:32 Robert Haas wrote:
>
>
> I notice that you say that the "Installation" section should "cover
> the architectural overview and point people to where they can find the
> stuff they need to install PostgreSQL in the various ways available to
> them" so maybe you're not
On Fri, Mar 22, 2024 at 7:10 AM Robert Haas wrote:
>
> That's actually what we had in chapter
> 18, "Installation from Source Code on Windows", since removed. But for
> some reason we decided that on non-Windows platforms, it needed a
> whole new chapter rather than an extra sentence in the
On Thu, Mar 21, 2024 at 11:30 AM Robert Haas wrote:
>
> My second thought is that the stuff from "VII. Internals" that I
> categorized as reference material should move into section "VI.
> Reference". I think we should also consider moving appendix F,
> "Additional Supplied Modules and
On Wed, Mar 20, 2024 at 9:43 AM Robert Haas wrote:
> On Tue, Mar 19, 2024 at 5:39 PM Andrew Dunstan
> wrote:
> > +many for improving the index.
>
> Here's a series of four patches.
I reviewed the most recent set of 5 patches.
> Taken together, they cut down the
> number of numbered chapters
On Sat, Mar 16, 2024 at 1:00 PM Étienne BERSAC
wrote:
>
> > The choice of warning is made because after the command ends the
> > grantmin question does not exist. The revoke was a no-op and the
> > final state is as the user intended.
>
>
> Sorry, can you explain me what's the grantmin question
On Thursday, March 14, 2024, Étienne BERSAC
wrote:
>
> However, I'd prefer if Postgres fails properly. Because the GRANT is
> actually not revoked. This prevent ldap2pg to report an issue in
> handling privileges on such roles.
>
> What do you think of make this warning an error ?
>
>
The choice
On Tuesday, March 12, 2024, adjk...@126.com wrote:
>
> Nee we change the title of the case-when output column?
>
>
Choosing either a or b as the label seems wrong and probably worth changing
to something that has no meaning and encourages the application of a column
alias.
David J.
On Mon, Feb 26, 2024 at 6:54 PM Andy Fan wrote:
>
> "David G. Johnston" writes:
>
> > On Mon, Feb 26, 2024 at 5:46 PM Andy Fan wrote:
> >
> > > Per recent discussion[1], plpgsql returns fairly unhelpful "syntax
> > > error&q
On Mon, Feb 26, 2024 at 5:46 PM Andy Fan wrote:
> > Per recent discussion[1], plpgsql returns fairly unhelpful "syntax
> > error" messages when a %TYPE or %ROWTYPE construct references a
> > nonexistent object. Here's a quick little finger exercise to try
> > to improve that.
>
> Looks this
On Mon, Feb 12, 2024 at 2:29 PM Pavel Luzanov
wrote:
> regress_du_role1 | no| Inherit | no| 2024-12-31
> 00:00:00+03(invalid) | 50 | Group role without password but
> with valid until
> regress_du_role2 | yes | Inherit | yes |
On Fri, Feb 16, 2024 at 1:16 PM Jim Jones wrote:
> In case all columns of a record have been set to null due to data type
> incompatibility, should we insert it at all?
Yes. In particular not all columns in the table need be specified in the
copy command so while the parsed input data is all
On Fri, Feb 9, 2024, 12:05 Deepak M wrote:
> Hello Hackers,
>
Wrong list, this is for discussions regarding patches.
> Folks, When tried to create a function with the same signature as
> procedure it fails.
>
That seems like a good hint you cannot do it. Specifically because they
get
On Wednesday, February 7, 2024, Joel Jacobson wrote:
>
> On Fri, Sep 8, 2023, at 23:43, Magnus Hagander wrote:
> > We need a "allowlist" of things a user can do, rather than a blocklist
> > of "they can do everything they can possibly think of and a computer
> > is capable of doing, except for
On Tue, Feb 6, 2024 at 7:10 AM Peter Eisentraut
wrote:
>
> How about ALTER SYSTEM is disabled if the file
> postgresql.auto.conf.disabled exists? This is somewhat similar to making
> the file read-only, but doesn't risk other tools breaking when they
> encounter such a file. And it's more
On Monday, February 5, 2024, Graham Leggett wrote:
>
> Also, how do you handle the race condition between the time a database db3
> is created, and the the time all readonly users have their access revoked
> to db3?
>
>
You alter the default privileges for the system so PUBLIC does not get
On Sun, Feb 4, 2024 at 5:04 PM Graham Leggett wrote:
> Hi all,
>
> I have a postgresql 15 instance with two databases in it, and I have a
> need to grant read-only access to one of those databases to a given user.
>
> To do this I created a dedicated role for readonly access to the database
>
On Fri, Feb 2, 2024 at 2:23 PM David G. Johnston
wrote:
> On Mon, Jan 15, 2024 at 4:35 AM Aleksander Alekseev <
> aleksan...@timescale.com> wrote:
>
>> PFA the patch. It's short but I think it mitigates the problem.
>>
>>
> I took a look at where these option
th the additional changes.
David J.
From adc6c807d2bc0d73271b47e4d1908e5c069e5b24 Mon Sep 17 00:00:00 2001
From: "David G. Johnston"
Date: Fri, 2 Feb 2024 14:16:24 -0700
Subject: [PATCH] v4 configs review
---
doc/src/sgml/config.sgml | 11 ++-
doc/src/sgml/libpq.sgml
t; On Sep 17, 2023, at 10:58 PM, David G. Johnston <
> david.g.johns...@gmail.com> wrote:
>
> > Parses a string of text, extracts a potential type name from it, and
> translates that name into an OID. Failure to extract a valid potential
> type name results in a
On Thu, Feb 1, 2024 at 11:59 PM Yugo NAGATA wrote:
>
> I attached a updated patch including fixes you pointed out above.
>
>
Removed "which"; changed "occupying" to "occupy"
Removed on of the two "amounts"
Changed "unacceptable to the input function" to just "converting" as that
is what the
Mon Sep 17 00:00:00 2001
From: "David G. Johnston"
Date: Thu, 1 Feb 2024 15:24:30 -0700
Subject: [PATCH] docs: improve hostssl related descriptions and option
presentation
runtime.sgml discussion regarding SSL was repetitive with itself
and presented in a problematic order - with discus
On Tuesday, January 30, 2024, Tom Lane wrote:
> "David G. Johnston" writes:
> > On Tuesday, January 30, 2024, Tom Lane wrote:
> >> My larger point here is that trying to enforce restrictions on
> >> superusers *within* Postgres is simply not a good pl
On Tuesday, January 30, 2024, Tom Lane wrote:
>
>
> My larger point here is that trying to enforce restrictions on
> superusers *within* Postgres is simply not a good plan, for
> largely the same reasons that Robert questioned making the
> GUC mechanism police itself. It needs to be done
On Sunday, January 28, 2024, Yugo NAGATA wrote:
> On Fri, 26 Jan 2024 08:04:45 -0700
> "David G. Johnston" wrote:
>
> > On Fri, Jan 26, 2024 at 2:30 AM Yugo NAGATA wrote:
> >
> > > On Fri, 26 Jan 2024 00:00:57 -0700
> > > "David G. Johnston
On Sun, Jan 28, 2024 at 4:51 PM jian he wrote:
> On Fri, Jan 26, 2024 at 11:09 PM David G. Johnston
> wrote:
> >
> > Hi,
> >
> > The option choice of "ignore" in the COPY ON_ERROR clause seems overly
> generic. There would seem to be two relevant wa
On Sun, Jan 28, 2024 at 1:29 PM Pavel Luzanov
wrote:
> I'd suggest pulling out this system view change into its own patch.
>
>
> But within this thread or new one?
>
>
>
Thread. The subject line needs to make clear we are proposing changing a
system view.
The connection limit can be set to 0.
On Fri, Jan 26, 2024 at 12:23 PM Tom Lane wrote:
>
> \set fbody `cat source_file.txt`
> CREATE FUNCTION foo() RETURNS whatever AS :'fbody' LANGUAGE ...;
>
> and maybe we should say that that's sufficient.
I really don't have a problem, and kinda prefer, using psql variables this
way but feel
On Thu, Jan 25, 2024 at 9:42 AM torikoshia
wrote:
> Hi,
>
> As described in 9e2d870119, COPY ON_EEOR is expected to have more
> "error_action".
> (Note that option name was changed by b725b7eec)
>
> I'd like to have a new option "log", which skips soft errors and logs
> information that should
On Fri, Jan 26, 2024 at 2:49 AM torikoshia
wrote:
> Hi,
>
> 9e2d870 enabled the COPY command to skip soft error, and I think we can
> add another option which specifies the maximum tolerable number of soft
> errors.
>
> I remember this was discussed in [1], and feel it would be useful when
>
Hi,
The option choice of "ignore" in the COPY ON_ERROR clause seems overly
generic. There would seem to be two relevant ways to ignore bad column
input data - drop the entire row or just set the column value to null. I
can see us wanting to provide the set to null option and in any case having
On Fri, Jan 26, 2024 at 2:30 AM Yugo NAGATA wrote:
> On Fri, 26 Jan 2024 00:00:57 -0700
> "David G. Johnston" wrote:
>
> > I will need to make this tweak and probably a couple others to my own
> > suggestions in 12 hours or so.
> >
>
>
And he
1 - 100 of 1056 matches
Mail list logo
