On 6/4/25 19:35, Thomas Munro wrote:
On Thu, Jun 5, 2025 at 3:44 AM Joe Conway wrote:
If you go from anything pre-glibc-2.21 to post-glibc-2.21 I think you
will find that even with the same data files you get a different sort.
The same patch that caused the performance regression [1] (still
On 6/4/25 09:52, Joe Conway wrote:
On 6/4/25 00:03, Thomas Munro wrote:
One way to move to a newer glibc-based Linux distribution but keep the
locales working the same* without keeping the associated zombie C code
alive is to find the source system's collation definition source
files, co
arget system and point
to the top-level directory with the environment variable LOCPATH.
I don't think this works in all cases because I have seen where sorting
was affected by C code rather than than data changes.
--
Joe Conway
PostgreSQL Contributors Team
Amazon Web Servi
gt; or do you think it ought to go just under the "General layout"
> syntax section?
I think we ought to show examples of each rules we're talking about in
each section.
That could be useful too, but I think complete examples are still good
to have.
--
Joe Conway
PostgreSQL Co
On 5/27/25 17:27, Bruce Momjian wrote:
On Mon, May 26, 2025 at 10:20:08AM -0400, Joe Conway wrote:
On 5/23/25 09:47, Bruce Momjian wrote:
> On Fri, May 23, 2025 at 09:54:54AM +0200, Álvaro Herrera wrote:
> > I also think that showing an XML-ish format of a commit message is
> >
?
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
On 4/11/25 16:26, Jonathan S. Katz wrote:
The Core Team would like to extend our congratulations to Jacob
Champion, who has accepted an invitation to become our newest PostgreSQL
committer.
Please join us in wishing Jacob much success and few reverts!
\o/
Congrats Jacob!
--
Joe Conway
the above needlessly confusing when we instead could use UTC
which is a more universally understood concept.
+1 for UTC.
+1
Seems to me we had this exact conversation at the last dev meeting in
Ottawa. How do we capture the decision for future versions of ourselves
to easily remember?
--
J
ke install; make
installcheck with a running instance). I think this would be very
convenient for extension development.
I LOVE this idea!
+many
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
oning from the server, for
instance.
+1 Robert articulates my thinking exactly, and much better than I did :-)
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
in my mind that might involve
the necessity of supporting multiple versions of unicode such that the
choice remains to remain on the older one.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
example, but allowing for others to be
plugged in via extensions.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
On 1/26/25 11:36, Andrew Dunstan wrote:
On 2025-01-26 Su 10:29 AM, Joe Conway wrote:
On 1/24/25 09:00, Andrew Dunstan wrote:
On 2025-01-24 Fr 7:25 AM, Peter Eisentraut wrote:
On 27.08.24 10:12, Peter Eisentraut wrote:
Here is a new patch version.
I simplified the uses of sed and awk
ds/main/PGBuild/Modules/TestSepgsql.pm)
Out of curiosity, what should have changed? I have so far done nothing
to rhino, yet it continues to return OK even after Peter's change...
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
e of these days...
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
On 1/24/25 08:55, Daniel Gustafsson wrote:
On 23 Jan 2025, at 21:42, Joe Conway wrote:
LGTM
After staring at it a bit more and fixing a few small details I committed this.
\o/
Thanks for getting this over the finish line!
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source
On 1/22/25 17:49, Daniel Gustafsson wrote:
On 22 Jan 2025, at 19:59, Joe Conway wrote:
I found it necessary to add:
#include
in
contrib/pgcrypto/openssl.c
to avoid a symbol not defined warning.
Makes sense, it doesn't reproduce in my tree but reading OpenSSL code it seems
very plau
On 1/21/25 17:57, Daniel Gustafsson wrote:
On 21 Jan 2025, at 22:13, Joe Conway wrote:
I think this is a non-issue. Every implementation I have seen, the OS-level
enabling of FIPS mode is just a way to ensure openssl is automatically put into
FIPS mode when the library is loaded, just as
SSL_VERSION_NUMBER >= 0x3000L
+ EVP_default_properties_is_fips_enabled(NULL);
+ #else
+ FIPS_mode();
+ #endif
+
+ return fips_enabled;
+ }
8<-
The we could call CheckFIPSMode() from CheckBuiltinCryptoMode() as well
as from a SQL-level wrapper.
--
Joe Conway
PostgreSQL Contributors Te
useful addition, but I guess one could derive the answer based on
whether these functions work or not when "builtin_crypto_enabled = fips"
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
;.
Maybe we could document that the test should fail if fips is enabled?
FWIW I have not tested at all on a fips enabled machine. I will see
about doing that...
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.comdiff --git a/contrib/pgcry
27;NFD') then
we'd need to also need to add CASEFOLD to gram.y (like NORMALIZE). Is
that a reasonable thing to do?
SQL 2023 seems to include the NORMALIZE syntax, but the only case
folding considered is UPPER and LOWER. As such, I think it ought to be a
function but not part of the gram
ommon terminology in
Postgres and Unicode, so "casefold" can be seen as the verb instead.
I don't have a strong opinion here so I will just go with whatever
seems like the popular choice.
FWIW I prefer casefold()
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
On 12/9/24 07:23, Daniel Gustafsson wrote:
On 4 Dec 2024, at 16:57, Joe Conway wrote:
I can send you the source RPM for openssl 1.1.1c which was an earlier FIPS
validated version, but the main FIPS patch contains:
AFAICT the forks of 1.1.1 which offer FIPS certification all patch the
can get buy in
given a high enough quality implementation, I would be excited to work
on it.
[1]
https://postgr.es/m/flat/CACA6kxgdzt-oForijaxfXHHhnZ1WBoVGMXVwFrJqUu-Hg3C-jA%40mail.gmail.com
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
On 12/4/24 10:57, Joe Conway wrote:
On 12/4/24 10:01, Daniel Gustafsson wrote:
On 4 Dec 2024, at 15:52, Joe Conway wrote:
On 12/4/24 09:45, Daniel Gustafsson wrote:
On 4 Dec 2024, at 15:40, Joe Conway wrote:
On 12/4/24 09:33, Daniel Gustafsson wrote:
since OpenSSL 1.1.1 cannot operate in
On 12/4/24 10:01, Daniel Gustafsson wrote:
On 4 Dec 2024, at 15:52, Joe Conway wrote:
On 12/4/24 09:45, Daniel Gustafsson wrote:
On 4 Dec 2024, at 15:40, Joe Conway wrote:
On 12/4/24 09:33, Daniel Gustafsson wrote:
since OpenSSL 1.1.1 cannot operate in FIPS mode.
I don't think th
On 12/4/24 09:45, Daniel Gustafsson wrote:
On 4 Dec 2024, at 15:40, Joe Conway wrote:
On 12/4/24 09:33, Daniel Gustafsson wrote:
since OpenSSL 1.1.1 cannot operate in FIPS mode.
I don't think that is correct. The RHEL 8 openssl which was FIPS 140-2
validated is 1.1.1k. See:
urity-policies/140sp4642.pdf
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
ere isn't a way
to make all of our lives easier going forward.
[1]
https://speakerdeck.com/clairegiordano/whats-in-a-postgres-major-release-an-analysis-of-contributions-in-the-v17-timeframe-claire-giordano-pgconf-eu-2024
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Sou
On 12/3/24 08:59, Daniel Gustafsson wrote:
On 24 Nov 2024, at 14:48, Daniel Gustafsson wrote:
Any other opinions or should we proceed with the proposed GUC?
I'm good with it. Did you want to commit or would you rather I do it?
--
Joe Conway
PostgreSQL Contributors Team
RDS Open S
is available in an
extension I wrote years ago (without the SQL grammar support) -- see
https://github.com/pgaudit/set_user
I have never proposed it (or maybe I did years ago, don't actually
remember) because I did not think the community was interested in this
approach, but perhaps the time is ripe to discuss it.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
On 11/22/24 09:11, Daniel Gustafsson wrote:
On 21 Nov 2024, at 22:39, Joe Conway wrote:
I mean, perhaps I am misreading and/or interpreting all of that differently to
you, but from my reading of the entire thread there was clearly no consensus to
using openssl to provide those two
On 11/21/24 15:43, Robert Haas wrote:
On Thu, Nov 21, 2024 at 2:06 PM Joe Conway wrote:
Because that idea was rejected earlier in the thread by multiple people
other than me?
¯\_(ツ)_/¯
I actually don't see that in the thread anywhere. Which messages are
you talking about?
Well
On 11/20/24 12:14, Daniel Gustafsson wrote:
On 19 Nov 2024, at 18:30, Joe Conway wrote:
Any other opinions out there?
Couldn't installations who would be satisfied with a GUC gate revoke privileges
from the relevant functions already today and achieve almost the same result?
I think
On 11/19/24 18:12, Robert Haas wrote:
On Tue, Nov 19, 2024 at 12:30 PM Joe Conway wrote:
Any other opinions out there?
Why should we accept your patch (which adds a legacy_crypto_enabled
GUC) instead of adopting the approach originally proposed (i.e. use
the OpenSSL version of the functions
On 10/29/24 10:08, Daniel Gustafsson wrote:
On 29 Oct 2024, at 13:53, Joe Conway wrote:
On 10/29/24 05:57, Daniel Gustafsson wrote:
On 26 Oct 2024, at 20:10, Joe Conway wrote:
Rather than depend on figuring out if we are in FIPS_mode in a
portable way, I think the GUC is simpler and
3897cdaccd02114
(1 row)
8<-
So both UPPER and INITCAP produce different results unless I am missing
something.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
On 10/29/24 12:52, Jacob Champion wrote:
On Sat, Oct 26, 2024 at 11:10 AM Joe Conway wrote:
Rather than depend on figuring out if we are in FIPS_mode in a portable
way, I think the GUC is simpler and sufficient. Why not do that and just
use a better name, e.g. legacy_crypto_enabled or
On 10/29/24 05:57, Daniel Gustafsson wrote:
On 26 Oct 2024, at 20:10, Joe Conway wrote:
Rather than depend on figuring out if we are in FIPS_mode in a portable way, I
think the GUC is simpler and sufficient. Why not do that and just use a better
name, e.g. legacy_crypto_enabled or
legacy_crypto_enabled or something similar
(bike-shedding welcomed) as in the attached.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.comdiff --git a/contrib/pgcrypto/expected/crypt-des.out b/contrib/pgcrypto/expected/crypt-des.o
When you have a fleet with no direct access to run shell commands, being
able to get this info via SQL is valuable.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
the crash on master and 17 stable branches, but not pg16
FWIW. That is as far as I have looked so far.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
ibxml2.so.2
[...]
Any feedback is appreciated.
I think it would be nice to include a sha256 hash (or something similar)
of the libraries as well, so that they can be checked against known good
values.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
er a connection
(which is all a lot of our users have access to).
+1
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
make this possible, no?
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
On 9/12/24 02:05, Thomas Munro wrote:
On Tue, Sep 10, 2024 at 3:04 PM Thomas Munro wrote:
On Mon, Sep 9, 2024 at 1:37 PM Joe Conway wrote:
Seems the mounted drive got unmounted somehow ¯\_(ツ)_/¯
Please check it out and let me know if it is working properly now.
Looks good, thanks
On 9/8/24 16:55, Thomas Munro wrote:
On Sat, Aug 3, 2024 at 12:07 AM Joe Conway wrote:
I tried making this run like a service using launchctl, but that was
giving the permissions errors. I finally gave up trying to figure it out
and just accepted that I need to manually start the script
exes by initial vowels is definitely
silly. On the other, I can see how it might be useful for an extension
to exclude indexes based on a regex match of the index name or something
similar, at least for testing.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
off period expedited.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
On 8/21/24 09:01, Peter Eisentraut wrote:
On 07.08.24 15:49, Daniel Gustafsson wrote:
On 5 Aug 2024, at 15:36, Joe Conway wrote:
It would not shock me to see complaints from others after we rip out support
for 1.0.2, but maybe not ¯\_(ツ)_/¯
I think it's highly likely that we wil
or is helpful (although I doubt it):
Error 503 Backend fetch failed
Backend fetch failed
Guru Meditation:
XID: 1030914118
I am not seeing any errors here. nagios monitoring is showing an ipv6
error though. Not the same issue as yesterday.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Sou
On 8/19/24 05:04, Jelte Fennema-Nio wrote:
On Sat, 17 Aug 2024 at 22:05, Joe Conway wrote:
Just to close this out -- problem found and fixed about an hour ago.
Sorry for the interruption.
Whatever the problem was it seems to have returned
What specifically? I am not seeing anything at the
oblem found and fixed about an hour ago.
Sorry for the interruption.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
um_l, isalpha_l, isascii_l, isblank_l, iscntrl_l, isdigit_l,
isgraph_l, islower_l, isprint_l, ispunct_l, isspace_l, isupper_l,
isxdigit_l
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
but maybe it
matters for some?
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
On 8/5/24 09:14, Tom Lane wrote:
Joe Conway writes:
I know I am way late to this thread, and I have only tried a cursory
skim of it given the length, but have we made any kind of announcement
(packagers at least?) that we intend to not support Postgres 18 with ssl
on RHEL 7.9 and derivatives
able until July 2028[1] which means
many people will continue to use it.
Joe
[1]
https://www.redhat.com/en/blog/announcing-4-years-extended-life-cycle-support-els-red-hat-enterprise-linux-7
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
On 8/2/24 11:07, Tom Lane wrote:
Joe Conway writes:
Hmmm, and then have "leakproof_mode" = strict/lax/off where 'strict' is
current behavior, 'lax' allows the 'maybe's to get pushed down, and
'off' ignores the leakproof attribute entirely
of attribute entirely and pushes down anything
that merits being pushed?
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
On 8/1/24 07:57, Robert Haas wrote:
On Wed, Jul 31, 2024 at 4:42 PM Joe Conway wrote:
You are assuming that everyone allows direct logins with the ability to
create procedures. Plenty don't.
Well, if you can send queries, then you can do the same thing, driven
by client-side logic.
On 8/1/24 07:17, Laurenz Albe wrote:
On Wed, 2024-07-31 at 14:43 -0400, Joe Conway wrote:
I still maintain that there is a whole host of users that would accept
the risk of side channel attacks via existence of an error or not, if
they could only be sure nothing sensitive leaks directly into
On 7/31/24 16:10, Robert Haas wrote:
On Wed, Jul 31, 2024 at 2:43 PM Joe Conway wrote:
I still maintain that there is a whole host of users that would accept
the risk of side channel attacks via existence of an error or not, if
they could only be sure nothing sensitive leaks directly into the
ime someone drops a bunch of new code in here.
I still maintain that there is a whole host of users that would accept
the risk of side channel attacks via existence of an error or not, if
they could only be sure nothing sensitive leaks directly into the logs
or to the clients. We should give
ful, but I know of users
that would accept that tradeoff in order to get better performance and
security on their production workloads. Or in some cases (e.g. PASSWORD)
just better security.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
On 7/23/24 10:44, Joe Conway wrote:
I guess if all else fails I will have to get the mac mini with more
built in storage in order to accommodate sonoma.
I *think* I finally have it in a good place. I replaced the nvme
enclosure that I bought the other day (which had a 10G interface speed
ly good tool on RHEL
variants, but I don't think many people use it on anything else. As Tom
says, perhaps there are a few wizards out there though...
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
rent state is
ok", and +1 on "current state is ok with agreement on what to do in 18"
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
I don't know to what
extent doing so would satisfy Noah's concern; but if it would do
so I'd be happy with that answer.
I came to the same conclusion. I think someone mentioned somewhere on
this thread that other databases support multiple Unicode versions. I
think we need to figu
e stuff removed the there is enough space?
I guess if all else fails I will have to get the mac mini with more
built in storage in order to accommodate sonoma.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
On 7/21/24 17:26, Thomas Munro wrote:
On Mon, Jul 22, 2024 at 8:34 AM Joe Conway wrote:
Hmmm, maybe nevermind? I rebooted the mac mini and now it seems to be
working. Maybe someone can confirm. There ought to be plenty of space
available for sonoma and ventura at the same time now.
Thanks
On 7/21/24 16:15, Joe Conway wrote:
On 7/18/24 10:33, Joe Conway wrote:
On 7/18/24 10:23, Nazir Bilal Yavuz wrote:
On Thu, 18 Jul 2024 at 17:01, Joe Conway wrote:
So perhaps I am back to needing more storage...
You might not need more storage. Thomas knows better, but AFAIU, CFBot
will
On 7/18/24 10:33, Joe Conway wrote:
On 7/18/24 10:23, Nazir Bilal Yavuz wrote:
On Thu, 18 Jul 2024 at 17:01, Joe Conway wrote:
So perhaps I am back to needing more storage...
You might not need more storage. Thomas knows better, but AFAIU, CFBot
will pull only sonoma images after the patch
On 7/18/24 10:23, Nazir Bilal Yavuz wrote:
On Thu, 18 Jul 2024 at 17:01, Joe Conway wrote:
So perhaps I am back to needing more storage...
You might not need more storage. Thomas knows better, but AFAIU, CFBot
will pull only sonoma images after the patch in this thread gets
merged. And your
On 7/18/24 08:55, Nazir Bilal Yavuz wrote:
Hi,
On Thu, 18 Jul 2024 at 15:00, Joe Conway wrote:
On 7/18/24 07:55, Joe Conway wrote:
> On 7/18/24 04:12, Nazir Bilal Yavuz wrote:
>> Could it be pulling the ''macos-runner:sonoma' image on every run?
>
> Or perhaps s
On 7/18/24 07:55, Joe Conway wrote:
On 7/18/24 04:12, Nazir Bilal Yavuz wrote:
Could it be pulling the ''macos-runner:sonoma' image on every run?
Or perhaps since this was the first run it simply needed to pull the
image for the first time?
The scheduling timing (21:24) looks
On 7/18/24 04:12, Nazir Bilal Yavuz wrote:
Hi,
On Thu, 18 Jul 2024 at 07:40, Thomas Munro wrote:
On Thu, Jul 18, 2024 at 9:58 AM Joe Conway wrote:
> On 7/17/24 16:41, Andres Freund wrote:
> > Does "tart pull ghcr.io/cirruslabs/macos-runner:sonoma" as the CI user
> &g
On 7/17/24 16:41, Andres Freund wrote:
Hi,
On 2024-07-17 13:20:06 -0400, Joe Conway wrote:
> > Or maybe simpler -- how do people typically add storage to a mac mini? I
> > don't mind buying an external disk or whatever.
>
> That I do not know, not a mac person at all..
On 7/17/24 13:01, Andres Freund wrote:
On 2024-07-16 12:12:37 -0400, Joe Conway wrote:
> It's possible you have some old images stored as your user, check
> "tart list" for both users.
Hmm, this is not the easiest ever to parse for me...
Unfortunately due to the wrap
lecmds.c.
I think including version in the key makes most sense. Also do we even
have a mechanism to grab the commit sha in running code?
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
.
And it'll be confusing to have a mix of old/new line numbers.
Agreed.
I am going to try hard to get back to this sooner rather than later, but
realistically that might be in time for the September commitfest rather
than during this one.
--
Joe Conway
PostgreSQL Contributors Team
RD
On 7/16/24 16:16, Tom Lane wrote:
Joe Conway writes:
So you are proposing we add STATIC to VOLATILE/STABLE/IMMUTABLE (in the
third position before IMMUTABLE), give it IMMUTABLE semantics, mark
builtin functions that deserve it, and document with suitable caution
statements?
What is the
On 7/16/24 15:33, David G. Johnston wrote:
On Tue, Jul 16, 2024 at 11:57 AM Joe Conway <mailto:m...@joeconway.com>> wrote:
> There are two alternative philosophies:
>
> A. By choosing to use a Unicode-based function, the user has opted in
> to
, and allow those to be
used like we do IMMUTABLE except with appropriate warning labels. E.g.
something ("STABLE_VERSION"?) to mean "forever within a major version
lifetime" and something ("STABLE_SYSTEM?") to mean "as long as you don't
upgrade your OS".
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
On 7/16/24 11:44, Andres Freund wrote:
hi,
On 2024-07-16 09:38:21 -0400, Joe Conway wrote:
On 7/16/24 08:28, Joe Conway wrote:
> On 7/16/24 00:34, Thomas Munro wrote:
> > temporarily disabled that machine from the pool and click the re-run
> > button, and it failed[2] on jc-m2
On 7/16/24 08:28, Joe Conway wrote:
On 7/16/24 00:34, Thomas Munro wrote:
temporarily disabled that machine from the pool and click the re-run
button, and it failed[2] on jc-m2-1: "Error: The operation couldn’t be
completed. No space left on device" after a long period during wh
that image. I could try this
experiment again if Joe could see a way to free up some disk space.
Hmmm, sorry, will take a look now
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
On 7/8/24 11:38, Joe Conway wrote:
On 7/3/24 12:51, Andrey M. Borodin wrote:
On 3 Jul 2024, at 01:08, Corey Huinker wrote:
I'll give it a shot.
Great, thank you! Do you have extended access to CF? Like activity log and
mass-mail functions?
If no I think someone from PG_INFRA can gran
that, although given that Corey and I are colleagues, it might
be better if someone else on pginfra did.
Or at least if a few other hackers tell me to "just do it"...
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
difficulty fetching the image? CCing our Mac Mini pool attendants.
How can I help? Do you need to know versions of some of the stuff on my
mac mini?
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
ughts on how to improve I am happy to make more changes.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
he policy written down somewhere, or is it only project lore? In
either case, what is the actual policy?
Thanks,
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
On 6/2/24 15:17, Neil Conway wrote:
Inspired by David Rowley's work [1]
Welcome back!
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
e likely to be taken seriously.
Maybe do a FOSDEM-style dev meeting with triage review at PG.EU would at
least move us forward? Granted it is less early and perhaps less often
than the thread seems to indicate, but has been tossed around before and
seems doable.
--
Joe Conway
PostgreSQL Contri
best sub-linearly (limited by the
velocity of knowledge sharing). I agree with Andrey on this, the only
way I see to handle this is to scale CF management efforts.
The number of items tracked are surely growing, but I am not sure I
would call it exponential -- see attached
--
Joe Conway
yeah, I'm
still here, please review my patch," we've already lost the game. That
person isn't sad because we asked them to click a link. They're sad
it's already been N * 2 months and nothing has happened.
+many
--
Joe Conway
PostgreSQL Contributors Team
RD
On 5/17/24 09:08, Peter Eisentraut wrote:
On 17.05.24 14:42, Joe Conway 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.
Becau
On 5/17/24 08:31, Jelte Fennema-Nio wrote:
On Fri, 17 May 2024 at 14:19, Joe Conway wrote:
On 5/16/24 22:26, Robert Haas wrote:
> For example, imagine that the CommitFest is FORCIBLY empty
> until a week before it starts. You can still register patches in the
> system generally, but
clear" - but I think that's
missing the point. What we really want is to not see that stuff in
the first place. It's a CommitFest, not
once-upon-a-time-I-wrote-a-patch-Fest.
+1
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
On 5/16/24 17:36, Jacob Champion wrote:
On Thu, May 16, 2024 at 2:29 PM Joe Conway wrote:
If no one, including the author (new or otherwise) is interested in
shepherding a particular patch, what chance does it have of ever getting
committed?
That's a very different thing from what I
1 - 100 of 511 matches
Mail list logo
