he new text is:
SELECT * will now output those columns for the many
system tables which have them. Previously, the columns had to be
selected
explicitly.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
fix src/tools/version_stamp.pl.
> (Looks like there's a reference in .gitattributes, too)
Yes, please remove.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
On Tue, May 14, 2019 at 11:53:23AM +0200, nickb wrote:
> On Sat, May 11, 2019, at 22:33, Bruce Momjian wrote:
> > http://momjian.us/pgsql_docs/release-12.html
>
> There is a typo in E.1.3.1.1.:
> > Expressions are evaluated at table partitioned table creation time.
> F
https://www.postgresql.org/message-id/flat/CAEepm%3D0P3FeTXRcU5B2W3jv3PgRVZ-kGUXLGfd42FFhUROO3ug%40mail.gmail.com
>
> ? The required change in pg_bsd_indent isn't quite done, but it
> could be done by next week.
Yes, I think we are good with everything above. I am thinking you
should do the run
es to avoid spurious
> > conflicts?
>
> I dunno, how far back are you thinking? I've occasionally wished we
> could reindent all the back branches to match HEAD, but realistically,
> people carrying out-of-tree patches would scream.
My regular back
out_ time zone columns, the
new data would take your local time and assume it was stored in UTC,
which I don't think you want. I don't know of a way to make the
adjustment you want without a table rewrite. It is unfortunate that the
SQL standard requires timestamp _without_ time zone to be
On Tue, May 21, 2019 at 09:09:10AM -0700, Shawn Debnath wrote:
> On Sat, May 11, 2019 at 04:33:24PM -0400, Bruce Momjian wrote:
> > I have posted a draft copy of the PG 12 release notes here:
> >
> > http://momjian.us/pgsql_docs/release-12.html
> >
> > They a
qOn Mon, May 20, 2019 at 03:17:19PM -0700, Andres Freund wrote:
> Hi,
>
> Note that I've added a few questions to individuals involved with
> specific points. If you're in the To: list, please search for your name.
>
>
> On 2019-05-11 16:33:24 -0400, Bruce Mom
preserve
the exact binary value is output. The previous behavior can be
restored by setting to zero.
Am I missing something?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
dekar, David Rowley, Dimitri Golgov
> >otherwise?
> >
> >I think it might actually make sense to take David off this list,
> >because his tableam work is essentially part of it's own entry, as
>
> Yeah, please take me off that one. My focus there wa
on that is declared to return RECORD
>(Elvis Pranskevichus)
>
> You could link to "queries-tablefunctions" which describes the column
> definition business; it's much more specific than "sql-createfunction".
Done.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
; >> in rare cases.
> >>
> >>
>
> It's probably worth mentioning, but I'd say something like
>
> Fix bugs that could cause ALTER TABLE DETACH PARTITION
> to not drop objects that should be dropped, such as
> automatically-created child indexes.
>
> The rest of it is not terribly interesting from a user's standpoint,
> I think.
Done.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
nation about the benefits?
>
> It could stand to say something about the benefits. As I said, there
> is already a little bit about the benefits, but that ended up being
> tied to the "Improve speed of btree index insertions" item. Moving
> that snippet to the correct it
On Tue, May 21, 2019 at 05:00:31PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > On Mon, May 20, 2019 at 08:48:15PM -0400, Tom Lane wrote:
> >> Yes, this should be in "source code". I think it should be merged
> >> with a391ff3c and 74dfe58a into somet
s:
https://tools.ietf.org/html/draft-badra-tls-key-exchange-00
Of course, that is just a guess.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
ch any
> > other partition
>
> Sorry for the slow turnaround on this. Excellent suggestion. I have
> updated the patches, please see attached.
Patch applied:
https://git.postgresql.org/pg/commitdiff/6eb612fea9d080f2ae77ecb7091e73dc9f298c97
--
On Mon, Oct 8, 2018 at 12:05:03PM +0200, Adrien NAYRAT wrote:
> On 9/20/18 8:47 AM, Adrien Nayrat wrote:
> >On 8/25/18 11:24 PM, Peter Geoghegan wrote:
> >>On Sat, Aug 25, 2018 at 2:18 PM, Bruce Momjian wrote:
> >>>>I think that's less "
On Mon, Oct 8, 2018 at 12:42:39PM +0200, Peter Eisentraut wrote:
> On 05/10/2018 19:01, Bruce Momjian wrote:
> > On Fri, Oct 5, 2018 at 04:53:34PM +0200, Peter Eisentraut wrote:
> >> On 23/05/2018 08:46, Heikki Linnakangas wrote:
> >>> "tls-unique" and &qu
On Mon, Oct 8, 2018 at 05:44:32PM +0200, Adrien NAYRAT wrote:
> On 10/8/18 5:20 PM, Bruce Momjian wrote:
> >Uh, where are you looking? We don't rebuild the beta docs until the
> >next beta release, but you can see the changes in the developer docs:
> >
> >
lone and copy have
non-destructive behavior on the old cluster once started, so it does
make some sense to merge them, unlike link.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
On Wed, Oct 10, 2018 at 12:55:33PM -0700, Andres Freund wrote:
> Hi,
>
> On 2018-10-08 21:28:02 -0400, Bruce Momjian wrote:
> > On Mon, Oct 8, 2018 at 05:44:32PM +0200, Adrien NAYRAT wrote:
> > > On 10/8/18 5:20 PM, Bruce Momjian wrote:
> > > >Uh, where ar
On Wed, Oct 10, 2018 at 06:06:01PM -0400, Bruce Momjian wrote:
> On Wed, Oct 10, 2018 at 12:55:33PM -0700, Andres Freund wrote:
> > Several people argued for introducing it, you're the only one that was
> > against it. Adrien, Amit Kapila, Peter Geoghegan, and I all said we
&g
On Wed, Oct 10, 2018 at 06:13:56PM -0400, Bruce Momjian wrote:
> On Wed, Oct 10, 2018 at 06:06:01PM -0400, Bruce Momjian wrote:
> > On Wed, Oct 10, 2018 at 12:55:33PM -0700, Andres Freund wrote:
> > > Several people argued for introducing it, you're the only one that was
&
or both.
Yes, I had the same reaction. Activity not involving other Postgres
members seems like it would not be covered by the CoC, except for
"behavior that may bring the PostgreSQL project into disrepute", which
seems like a stretch.
--
Bruce Momjian http://momjian.us
E
to see the new
time zone change date.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
file /etc/ssl/openssl.cnf -extensions v3_ca \
> - -signkey root.key -out root.crt
>
> Finally, create a server certificate signed by the new root certificate
> authority:
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
On Tue, Oct 16, 2018 at 02:02:48PM +0200, Magnus Hagander wrote:
>
>
> On Tue, Oct 16, 2018 at 4:49 AM Bruce Momjian wrote:
>
> On Tue, Oct 16, 2018 at 11:45:53AM +0900, Tatsuo Ishii wrote:
> > > I'm not opposed to simplifying the instructions, however.
&g
ke to suppress them but I don't know how.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
On Mon, Nov 5, 2018 at 01:01:47PM +0700, John Naylor wrote:
> On 11/5/18, Bruce Momjian wrote:
> > During make --silent, I occasionally see these lines:
> >
> > Writing postgres.bki
> > Writing schemapg.h
> > Writing postgres.description
>
e Oracle ASH.
>
> If so, does sampling have no significant impact on performance? Even if the
> interval is 0.01 s or more.
I am replying late, but one of the reasons that sampling is used is that
decreasing the sampling interval increases to overhead of the sampling
process, but doesn'
On Wed, Nov 28, 2018 at 03:25:34PM +0900, Etsuro Fujita wrote:
> Here is a small patch for removing $SUBJECT.
Agreed. Patch applied through PG 10, where this first appeared.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+
s.]
I remember the good performance numbers from this feature. How does
this interact with the JIT executor feature, which is also designed to
speed up the executor? Is it something that can be combined with JIT?
--
Bruce Momjian http://momjian.us
EnterpriseDB
On Wed, Nov 28, 2018 at 10:46:51AM -0300, Alvaro Herrera wrote:
> On 2018-Nov-28, Bruce Momjian wrote:
>
> > On Wed, Nov 28, 2018 at 03:25:34PM +0900, Etsuro Fujita wrote:
> > > Here is a small patch for removing $SUBJECT.
> >
> > Agreed. Patch applied through
On Wed, Nov 28, 2018 at 08:51:54AM -0500, Bruce Momjian wrote:
> On Wed, Nov 28, 2018 at 10:46:51AM -0300, Alvaro Herrera wrote:
> > On 2018-Nov-28, Bruce Momjian wrote:
> >
> > > On Wed, Nov 28, 2018 at 03:25:34PM +0900, Etsuro Fujita wrote:
> > > > Here is
ht not like that.
>
> Any thoughts from others about whether to rename clientdn to client_dn
> to allow better naming of the new fields?
Makes sense. The SSL acronyms can get very complex.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
#x27;t support elliptic curve. Chrome accessing mail.google.com
is already using ECDSA:
https://momjian.us/main/writings/pgsql/tls.pdf#page=16
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
tion to work, the drain/switch over
time could be significant.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
probability of suboptimal plans increases.
I think the fact that pgbench shows a 2x improvement for prepared
statements, and real world reports are a 10% improvement means we need
to have a better understanding of exactly what workloads can benefit
from this, and a comprehensive analysis of all th
eed a hack to get the
> pg_bsd_indent executable.
So your point is that pg_bsd_indent and pgindent are in the source tree,
but not in any package distribution? Isn't that a packager decision?
--
Bruce Momjian https://momjian.us
EDB https://enterprise
uot; upstream. Packagers
> are probably more likely to package the tools if they are marked for
> installation by upstream too.
>
> Hope this helps to better explain what changes would be required within the
> Postgres source tree.
Yes, it does, thanks.
--
Bruce Momjian
tion, preventing higher priority processes from
> progressing.
>
> I doubt you can implement this in a robust manner outside of postgres.
FYI, here is an article about priority inversion:
https://www.geeksforgeeks.org/priority-inversion-what-the-heck/
--
Bruce Momjian
direction
> by somebody hammering on the side of the argument that they believe to
> be correct and ignoring the other one.
What if we generate log messages when certain commands are used, like
ALTER TABLE? We could have GUC which controls which commands are
logged.
--
Bruce Momjian
o do with the
> growing popularity and success of PostgreSQL. If you have more people
> using your software, you're also going to have more people using
> out-of-date versions of your software.
Yeah, probably, and we recently end-of-life'ed PG 11.
--
Bruce Momji
On Thu, Mar 14, 2024 at 10:46:28PM -0400, Bruce Momjian wrote:
> > In the end, while I certainly don't mind improving the web page, I
> > think that a lot of what we're seeing here probably has to do with the
> > growing popularity and success of PostgreSQL. If you hav
explanation,
> except you said it better than I would have done.
I do think the docs need to clearly say this is not a security feature.
In fact, I wonder if the ALTER SYSTEM error message should explain the
GUC that is causing the failure.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
ersion < PG_VERSION_NUM)
partial_agg_ok = false;
}
It uses check_partial_aggregate_support, which defaults to false,
meaning partial aggregates will be pushed down with no version check by
default. If set to true, pushdown will happen if the remote server is
the same version or newer, which seems acceptable to me.
FYI, the patch is much smaller now. :-)
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
; I'm not super thrilled by the fact that the patch contains zero
> user-facing documentation, even though it's created new SQL syntax,
> not to mention a new postgres_fdw option. I assume this means that
> nobody thinks it's anywhere near ready to commit.
Previous versions
I think this kind of doc structure review is long overdue.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
ch. The patch that Mr. Momjian reviewed
> is this.
> If user-facing documentation is needed for this POC patch, it can be added.
>
> I apologize for the lack of explanation regarding this positioning, which may
> have caused misunderstandings regarding the patch posted in [3
me it was just that way because it's the default setting of the
> > stylesheets.
>
> That's quite possible. I don't have strong opinions on whether we should
> change, or keep it the way it is.
If we can't justify why it should be different, it should be like the
surrounding sections.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
r 27, under a chapter
Well, until this commit in 2022, the system views were _under_ the
system catalogs chapter:
commit 64d364bb39c
Author: Bruce Momjian
Date: Thu Jul 14 16:07:12 2022 -0400
doc: move system views section to its own chapter
years we
thought we didn't need fsync since the BSD file system was 8k at the
time.
What we later realized is that we have no guarantee that the file system
will write to the device in the specified block size, and even it it
does, the I/O layers between the OS and the device might not, si
storical accident, but maybe there was some other
> logic to it.
I assume statistics collector views are in "Monitoring Database
Activity" because that is their purpose.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
On Fri, Mar 22, 2024 at 03:13:29PM -0400, Robert Haas wrote:
> On Fri, Mar 22, 2024 at 2:59 PM Bruce Momjian wrote:
> > I assume statistics collector views are in "Monitoring Database
> > Activity" because that is their purpose.
>
> Well, yes. :-)
>
> But t
turn off
--> this page imaging by turning off the full_page_writes parameter.
--> Battery-Backed Unit (BBU) disk controllers do not prevent partial page
--> writes unless they guarantee that data is written to the BBU as full
--> (8kB) pages.
--
Bruce Momjian h
't "configuration" too generic a term for disabling ALTER SYSTEM?
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
remember is that some people modified the ZFS file
system parameters enough that they made Postgres non-durable and
corrupted their database. This is a very hard thing to get right
because the user has very little feedback when they break things.
--
Bruce Momjian https://momjian.
On Mon, Mar 25, 2024 at 09:40:55PM +0100, Jelte Fennema-Nio wrote:
> On Mon, 25 Mar 2024 at 20:16, Bruce Momjian wrote:
> > I am wondering if the fact that you would be able to do:
> >
> > ALTER SYSTEM SET externally_managed_configuration = false
> >
> >
On Tue, Mar 26, 2024 at 10:23:51AM -0400, Tom Lane wrote:
> Robert Haas writes:
> > On Mon, Mar 25, 2024 at 5:04 PM Bruce Momjian wrote:
> >> To me, externally_managed_configuration is promising a lot more than it
> >> delivers because there is still a lot
> +mechanism updates the configuration. Setting this parameter to
> +on can help to avoid such mistakes.
> +
"off"
Is this really a patch we think we can push into PG 17. I am having my
doubts.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
> > > > that outside
> > >
> > > "might"
> >
> > This does not seem like a mistake to me. I'm not sure why you think it is.
>
> I also think the original sentence was correct, but I don't think it
> read
>
> I agree, and have committed your 0001.
So, I email "Is this really a patch we think we can push into PG 17. I
am having my doubts," and the patch is applied a few hours after my
email. Wow.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
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 "allow_alter_system" since
change, let's just be careful since we have a bad
history of pushing things near the end that we regret. I am not saying
that would be this feature, but let's be careful.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
On Wed, Mar 27, 2024 at 03:20:38PM -0700, David G. Johnston wrote:
> On Wed, Mar 27, 2024 at 3:18 PM David G. Johnston
> 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:
>
generate_series(1,10) AS i;
>
> WITH edge AS (
> SELECT start_node, end_node
> FROM edge_data
> WHERE edge_id = 1
> )
> SELECT start_node id FROM edge UNION
> SELECT end_node FROM edge;
I can confirm the crash in git master.
--
Bruce Momjian
On Thu, Mar 28, 2024 at 12:47:46AM +0100, Jelte Fennema-Nio wrote:
> On Wed, 27 Mar 2024 at 23:06, Bruce Momjian wrote:
> > > > > > +some outside mechanism. In such environments, using
> > > > > > ALTER
> > > > > > +SYSTE
meter to off can
> +help to avoid such mistakes.
"help to avoid" -> "help avoid"
> +
> +
> +
> + This parameter only controls the use of ALTER
> SYSTEM.
> +The settings stored in postgresql.auto.conf
> always
&q
commitfest can be
a valid concern. I do agree with your analysis of other patches in the
commitfest, but I just don't see them stretching our boundaries like
this patch.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
els a little ... over-edited. But if you're happy with the latest
> version, we can go with that. Or, do you need more time to review?
I am fine with moving ahead. I thought my later emails explaining we
have to be careful communicated that.
--
Bruce Momjian http
it updates the
"discarding" -> "overwriting" ?
> +
> + ALTER SYSTEM can be disabled by setting
> +to off, but
> this
> + is no security mechanism (as explained in detail in the documentation for
"is no" -> "is not a"
--
Br
On Fri, Mar 29, 2024 at 08:46:33AM -0400, Robert Haas wrote:
> On Thu, Mar 28, 2024 at 3:33 PM Bruce Momjian wrote:
> > I am fine with moving ahead. I thought my later emails explaining we
> > have to be careful communicated that.
>
> OK. Thanks for clarifying. I've co
r committers are known
individuals, but this might have cautionary lessons for us.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
ow many of us
> would scrutinize it? Imagine hiding something bad in the middle of
> that file somewhere.
So, in this case, the hooks were in 'configure', but not configure.ac,
and the exploit was in a test file which was in the tarball but _not_ in
the git tree. So, they use
the patches in its source tarball.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
Reality check --- are we still targeting this feature for PG 17?
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
elease schedule.
I was more asking if users have access to patches so they could recreate
the build by using the Postgres git tree and supplied OS-specific
patches.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
doing major redesign of the behavior, nor adding fundamentally new
> monitoring capabilities.
I think pg_upgrade could check for the existence of extended statistics
in any database and adjust the analyze recommdnation wording
accordingly.
--
Bruce Momjian https://momjian.us
EDB
On Fri, Mar 29, 2024 at 06:37:24PM -0400, Bruce Momjian wrote:
> You might have seen reports today about a very complex exploit added to
> recent versions of liblzma. Fortunately, it was only enabled two months
> ago and has not been pushed to most stable operating systems like Deb
On Mon, Apr 1, 2024 at 03:17:55PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > I was more asking if users have access to patches so they could recreate
> > the build by using the Postgres git tree and supplied OS-specific
> > patches.
>
> AFAIK, every open-
about major releases, and then minor releases. This gives a more
natural flow.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
diff --git a/templates/support/versioning.html b/temp
bit) that we
> really consider all the older ones to be, well, obsolete. The difference
> "current vs obsolete" is stronger than "latest vs not quite latest".
Okay, I changed "superseded" to "old", and changed "latest" to
"current", pa
ments based on the community's suggestions.
>
> Thank you for considering my contribution.
Aside from an extra newline in the patch, I think this is ready to go!
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
On Wed, Apr 3, 2024 at 09:25:02AM -0400, Bruce Momjian wrote:
> On Wed, Apr 3, 2024 at 04:17:21PM +0300, Panda Developpeur wrote:
> > Dear PostgreSQL Hackers,
> >
> > I am submitting a patch to modify pg_ctl to detect the presence of a geek
> > user
> > on
f I agree it reads a bit odd
> otherwise. I think that has more to do with this being just the wrong
> structure to get our point across. Can we pick out some statistics from our
> long history of publishing minor releases to present an objective reality to
> the reader to convince t
f manual steps) from the user's perspective.
Yes, you are correct. It used to be under "modules" and we didn't
update this text, partly because this it not in our source git tree;
updated patch attached.
--
Bruce Momjian https://momjian.us
EDB
On Thu, Apr 4, 2024 at 04:38:10PM -0400, Greg Sabino Mullane wrote:
> On Thu, Apr 4, 2024 at 2:23 PM Bruce Momjian wrote:
> +Such upgrades might require manual changes to complete so always read
> +the release notes first.
>
> Proposal:
> "Such upgrades might r
ler set of keys and certificates. I haven't looked into what
> sort of savings that could yield (if any) but if we go the route of
> regeneration at test-time we shouldn't leave potential savings on the table.
Rather then everyone testing it on every build, couldn't we have an
aut
at \. is the only copy
backslash command where we define the behavior only alone at the
beginning of a line, and not in other circumstances. The \a example
above suggests \. should be period in all other cases, as suggested, but
I don't know the ramifications if that.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
e unable to communicate with us securely. I
suppose some special word could be used to communicate that status ---
that is how it was done in non-electronic communication in the past.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.
ause the committer to lose context of the patch and thus interest in
> the patch. And then finally getting into the exact same situation next
> year in the final commit fest, when some other committer didn't agree
> with the redesign of the first one and request a new one pu
pened. I learned to
write the paper with the ideas I had, and if I come up with a better
idea later, I can add it to the end.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
, have problems, and now we are requiring
Andres to stop what he is doing to give immediate feedback --- that is
not fair to him.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
e comments are thrown away. They do not appear in the existing
> Doxygen output.
I have found it very strange that a tool like doxygen which can create
all sorts of call graphs, just ignores some comments. The comments
above function are very important.
--
Bruce Momjian ht
visit this idea.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
ase.
Yes, the _minimal_ approach has changed in the past few years to make
pg_upgrade debugging easier. The original design was ultra-conservative
where it could be, considering how radical the core functionality was.
--
Bruce Momjian https://momjian.us
EDB
ere a way to make Outlook do the leading ">" in a reply
> for the previous message?
Here is a blog post about how complex email posting can be:
https://momjian.us/main/blogs/pgblog/2023.html#September_8_2023
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
-compatible with
> > clients that don't support longer keys.
>
> My intuition would be to make this a protocol version bump, not an optional
> feature. I think this is something that everyone should eventually be
> using, not a niche feature that you explicitly w
we can do? Should we
have a more consistent response for such reporters?
It would be a crazy idea to report something in the logs if a major
version is run after a certain date, since we know the date when major
versions will become unsupported.
--
Bruce Momjian https://momjia
On Mon, Mar 11, 2024 at 04:12:04PM -0500, Nathan Bossart wrote:
> On Mon, Mar 11, 2024 at 04:37:49PM -0400, Bruce Momjian wrote:
> > https://www.postgresql.org/support/versioning/
> >
> > This web page should correct the idea that "upgrades are more risky than
801 - 900 of 2731 matches
Mail list logo
