On Thu Apr 17, 2025 at 2:15 AM CDT, Jelte Fennema-Nio wrote:
> On Thu, 17 Apr 2025 at 03:57, Tristan Partin wrote:
>> I spent some time exploring the Meson build a bit, and I realized that
>> C++ support in PGXS is tied to LLVM enablement. Checking the autotools
>> buil
CXX =
CXXFLAGS =
...
This then accounts for the original pg_duckdb command line looking the
way that it did.
Attached is a patch which decouples C++ support in PGXS from LLVM for
a Meson-compiled Postgres.
[0]: https://github.com/duckdb/pg_duckdb
--
Tristan Partin
Neon (https://neon.tech)
F
Looks correct to me. TIPs 628[0] and 666[1] seem to be the proposals which added
Tcl_Size and changed functions to use the type.
Reviewed-by: Tristan Partin
[0]: https://core.tcl-lang.org/tips/doc/trunk/tip/628.md
[1]: https://core.tcl-lang.org/tips/doc/trunk/tip/666.md
--
Tristan Partin
On Mon Nov 11, 2024 at 5:53 AM CST, Amit Kapila wrote:
On Thu, Nov 7, 2024 at 4:40 PM Amit Kapila wrote:
On Thu, Nov 7, 2024 at 9:36 AM Tristan Partin wrote:
>
>
> Here is a patch which does so.
>
Note that this parameter also applies on the subscriber side, but with
ld a good default be?
--
Tristan Partin
Neon (https://neon.tech)
diff --git a/doc/src/sgml/Makefile b/doc/src/sgml/Makefile
index a04c532b53..6f629e02a7 100644
--- a/doc/src/sgml/Makefile
+++ b/doc/src/sgml/Makefile
@@ -130,6 +130,9 @@ html-stamp: stylesheet.xsl postgres-full.xml $(ALL_IMAGES)
$(XS
]:
https://www.postgresql.org/docs/17/runtime-config-replication.html#GUC-MAX-REPLICATION-SLOTS-SUBSCRIBER
--
Tristan Partin
Neon (https://neon.tech)
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index d54f904956..34b29fa13e 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src
require
using a well-known build system like PGXS or meson. There are probably
security implications that need to be worked through. The packaging team
could maybe have some burden lifted off their shoulders.
Is that something people would be interested in? As someone who writes
softw
.
FWIW, I ran into this compiling an extension written in C++ for v15, so
I'll throw my support for backpatching this if that is still on the
table. Understandable if not, though.
--
Tristan Partin
Neon (https://neon.tech)
On Fri Oct 25, 2024 at 3:19 PM CDT, Tom Lane wrote:
"Tristan Partin" writes:
FWIW, I ran into this compiling an extension written in C++ for v15, so
I'll throw my support for backpatching this if that is still on the
table. Understandable if not, though.
I'm incline
=tristan957.postgres-hacker
Good to know, I will try this later.
I am open to feature requests and contributions. Here is the repo:
https://git.sr.ht/~tristan957/vscode-postgres-hacker
--
Tristan Partin
Neon (https://neon.tech)
sted in your config, Peter. I've been using glow[0] to
render markdown in my terminal, but I don't have that configured with
less(1)[1].
[0]: https://github.com/charmbracelet/glow
[1]:
https://git.sr.ht/~tristan957/dotfiles/tree/5a267b7e0de260f814a1830f98c55d1accb9d72e/item/less/.config/environment.d/z-01-less.conf#L4
--
Tristan Partin
Neon (https://neon.tech)
this is
false positive report so maybe this deserves a patch?
I tried to apply your v2 patch set but v2-0004 seems out of date.
Thanks for giving it a try Junwang. I'll rebase this, hopefully tomorrow
and give it another push.
--
Tristan Partin
Neon (https://neon.tech)
ragma GCC bless end puts
}
I wonder if we could use function poisoning to our advantage. For
instance in ecpg, it looks like you got all of the strtod() invocations
and replaced them with strtod_l(). Here is a patch with an example of
what I'm talking about.
--
Tristan Partin
Neo
recognize it's a little bit of chicken-and-egg.
Thanks Greg. I'll send another email on that list and try to see what
I can do regarding a patch!
--
Tristan Partin
Neon (https://neon.tech)
lqwsue5...@neon.tech
--
Tristan Partin
Neon (https://neon.tech)
checked
in configure.ac.
Author: Wolfgang Walther
Reviewed-by: Nazir Bilal Yavuz, Alvaro Herrera, Peter Eisentraut
Reviewed-by: Tristan Partin
Discussion:
https://www.postgresql.org/message-id/ca8f37e1-a2c3-40e2-91f6-59c3d3652...@technowledgy.de
Backpatch: 16-, where meson sup
://www.officeholidays.com/ics-clean/usa
[1]: https://www.postgresql.org/developer/roadmap/
--
Tristan Partin
Neon (https://neon.tech)
Heikki asked me to take a look at this patchset for the commitfest.
Looks good to me.
Heikki, just be careful rebasing the first patch. You need to make sure
the newly set `required: false` gets carried forward.
--
Tristan Partin
Neon (https://neon.tech)
s like we could help future
us out by teaching compiler.find_library() to take a list of names to
look at similar to how dependency() works now.
Reviewed-by: Tristan Partin
--
Tristan Partin
Neon (https://neon.tech)
our thoughts!
[0]: https://mesonbuild.com/Wrap-dependency-system-manual.html
[1]:
https://github.com/hse-project/hse/blob/6d5207f88044a3bd9b3539260074395317e276d5/meson.build#L239-L275
[2]:
https://github.com/hse-project/hse/blob/6d5207f88044a3bd9b3539260074395317e276d5/subprojects/packagefiles/libbsd/meson.build
--
Tristan Partin
https://tristan.partin.io
On Wed Jun 5, 2024 at 3:56 PM CDT, Robert Haas wrote:
On Wed, Jun 5, 2024 at 4:32 PM Tristan Partin wrote:
> Not entirely sure how I feel about the approach you've taken, but here
> is a patch that Heikki and I put together for extension compatibility.
> It's not a build t
-processing without recompiling has
value.
--
Tristan Partin
https://tristan.partin.io
From 60b0225d8e82d412237297710a7f007b006a7773 Mon Sep 17 00:00:00 2001
From: Tristan Partin
Date: Thu, 31 Aug 2023 11:08:01 -0500
Subject: [PATCH] Add PG_MODULE_MAGIC_REENTRANT
Extensions should use this if and
On Sun Jun 2, 2024 at 12:25 AM CDT, Tom Lane wrote:
"Tristan Partin" writes:
> On Fri May 31, 2024 at 12:02 PM CDT, Ashutosh Bapat wrote:
>> We talked this off-list at the conference. It seems we have to somehow
>> avoid passing pg_regress --schedule argument and
meson test -C build regress/regress --test-args "--no-schedule
my_specific_test"
Does anyone have an opinion?
--
Tristan Partin
https://tristan.partin.io
, but that's also a big ask and we'd
probably still not have it.
Not sure how useful it would be as an example, but MariaDB has
a blackhole storage engine[0], which has helped serve as a guide for me
previously.
[0]: https://mariadb.com/kb/en/blackhole/
--
Tristan Pa
LIBZ', 1)
endif
endif
You can see that we do pass the include dirs to the has_header check.
Something seems to be going wrong here since your extra_include_dirs
isn't being properly translated to include arguments.
--
Tristan Partin
https://tristan.partin.io
On Tue May 7, 2024 at 1:29 PM CDT, Andres Freund wrote:
Hi,
On 2024-05-06 14:07:53 -0500, Tristan Partin wrote:
> Instead of needing to be explicit, we can just iterate the
> pgstat_kind_infos array to find the memory locations to read into.
> This was originally thought of by
On Tue May 7, 2024 at 1:01 AM CDT, Michael Paquier wrote:
On Tue, May 07, 2024 at 12:44:51AM -0500, Tristan Partin wrote:
> Thanks for the feedback Michael. Should I just throw the patch in the next
> commitfest so it doesn't get left behind?
Better to do so, yes. I have noted thi
On Mon May 6, 2024 at 9:50 PM CDT, Michael Paquier wrote:
On Mon, May 06, 2024 at 02:07:53PM -0500, Tristan Partin wrote:
> This was originally thought of by Andres in
> 5891c7a8ed8f2d3d577e7eea34dacff12d7b6bbd.
+1 because you are removing a duplication between the order of the
it
lead to someone deleting the comment, and keeping the code
as is. Either way, a win :).
--
Tristan Partin
Neon (https://neon.tech)
From 5cc5a67edbd3dee145ea582c024b6ee207ae4085 Mon Sep 17 00:00:00 2001
From: Tristan Partin
Date: Mon, 6 May 2024 13:52:58 -0500
Subject: [PATCH v1] Use
I thought that this might be a small quality of life improvement for
people scrolling through logs wondering which tranche name wasn't
registered.
--
Tristan Partin
Neon (https://neon.tech)
From 63c8d92a8a82acc5f8859ab47da5105cef46b88e Mon Sep 17 00:00:00 2001
From: Tristan Partin
Date
dvocate for any PRs from AIX folks on the Meson side. You
can find me as @tristan957 on github.
--
Tristan Partin
Neon (https://neon.tech)
On Wed Jan 24, 2024 at 11:57 AM CST, Tristan Partin wrote:
On Wed Jan 24, 2024 at 10:18 AM CST, Tristan Partin wrote:
> On Tue Jan 23, 2024 at 3:30 AM CST, Peter Eisentraut wrote:
> > On 22.01.24 21:04, Tristan Partin wrote:
> > 3. Meson does not support tar.bz2 archives.
today. Looks like your patch is messed
up? You seem to have more of the diff at the bottom which seems to add
a test. Want to send a v2 with a properly formatted patch?
Example command:
git format-patch -v2 -M HEAD^
--
Tristan Partin
Neon (https://neon.tech)
Thanks Jelte and Robert for the extra effort to correct my mistake.
I apologize. Bad copy-paste from a previous revision of the patch at
some point.
--
Tristan Partin
Neon (https://neon.tech)
On Wed Apr 3, 2024 at 10:05 AM CDT, Jelte Fennema-Nio wrote:
On Wed, 3 Apr 2024 at 16:55, Tristan Partin wrote:
> Removing from the switch statement causes a warning:
>
> > [1/2] Compiling C object src/bin/psql/psql.p/command.c.o
> > ../src/bin/psql/command.c: In function ‘wa
c.o
../src/bin/psql/command.c: In function ‘wait_until_connected’:
../src/bin/psql/command.c:3803:17: warning: enumeration value
‘PGRES_POLLING_ACTIVE’ not handled in switch [-Wswitch]
3803 | switch (PQconnectPoll(conn))
| ^~
--
Tristan Partin
Neon (https://neon.tech)
lls.
Patches look good. Sorry about causing you to do some work.
--
Tristan Partin
Neon (https://neon.tech)
On Tue Apr 2, 2024 at 9:32 AM CDT, Robert Haas wrote:
On Mon, Apr 1, 2024 at 12:04 PM Tristan Partin wrote:
> > This sentence seems a bit contorted to me, like maybe Yoda wrote it.
>
> Incorporated feedback, I have :).
Committed it, I did. My thanks for working on this iss
at
version exists in the base repo. Perhaps it is 0.55, which would still
get rid of the aforementioned warning.
Committer, please pick your patch :).
[0]:
https://www.postgresql.org/message-id/40e80f77-a294-4f29-a16f-e21bc7bc7...@eisentraut.org
--
Tristan Partin
Neon (https://neon.tech)
d
On Mon Mar 25, 2024 at 1:44 PM CDT, Robert Haas wrote:
On Fri, Mar 22, 2024 at 4:58 PM Tristan Partin wrote:
> I had a question about parameter naming. Right now I have a mix of
> camel-case and snake-case in the function signature since that is what
> I inherited. Should I change t
d to look at the
situation again though.
[0]: If someone wants to make a plea here:
https://github.com/mesonbuild/meson/pull/12623
--
Tristan Partin
Neon (https://neon.tech)
ar.bz2',
+ )
You might find Meson's string formatting syntax creates a more readable
command string:
'tar.tar.bz2.command=@0@ -c'.format(bzip2.path())
And then 'install: false' is the default if you feel like leaving it
out.
Otherwise, let's get this in!
--
Tristan Partin
Neon (https://neon.tech)
On Fri Mar 22, 2024 at 12:17 PM CDT, Robert Haas wrote:
On Fri, Mar 22, 2024 at 1:05 PM Tristan Partin wrote:
> Sorry for taking a while to get back to y'all. I have taken your
> feedback into consideration for v9. This is my first time writing
> Postgres docs, so I'm ready f
eful even if we don't take the full CI patch (0003).
0002 looks pretty reasonable to me.
About the 0003 patch: It seems useful in principle to test these things
continuously. The dist script runs about 10 seconds in each task, and
takes a bit of disk space for the artifacts. I'm not sure to what
degree this might bother someone.
0003 works for me :).
--
Tristan Partin
Neon (https://neon.tech)
On Fri Mar 22, 2024 at 9:59 AM CDT, Robert Haas wrote:
On Wed, Jan 31, 2024 at 1:07 PM Tristan Partin wrote:
> I was looking for documentation of PQsocket(), but didn't find any
> standalone (unless I completely missed it). So I just copied how
> PQsocket() is documented in PQco
On Thu Mar 14, 2024 at 12:15 AM CDT, Michael Paquier wrote:
On Thu, Mar 14, 2024 at 12:13:18AM -0500, Tristan Partin wrote:
> One of them adds version gates to two LLVM flags (-frwapv,
> -fno-strict-aliasing). I believe we moved the minimum LLVM version recently,
> so these mig
iables into the PGXS Makefile.
--
Tristan Partin
Neon (https://neon.tech)
On Tue Mar 12, 2024 at 6:56 PM CDT, Sutou Kouhei wrote:
Hi,
In
"Re: meson: Specify -Wformat as a common warning flag for extensions" on Fri,
08 Mar 2024 10:05:27 -0600,
"Tristan Partin" wrote:
> Ok, I figured this out. -Wall implies -Wformat=1. We set warning_le
On Fri Mar 8, 2024 at 12:32 AM CST, Michael Paquier wrote:
On Thu, Mar 07, 2024 at 11:39:39PM -0600, Tristan Partin wrote:
> It sounds like a legitimate issue. I have confirmed the issue exists with a
> pg_config compiled with Meson. I can also confirm that this issue exists in
> the
e confirmed the issue exists
with a pg_config compiled with Meson. I can also confirm that this issue
exists in the autotools build.
Here is a v2 of your patch which includes the fix for autotools. I will
mark this "Ready for Committer" in the commitfest. Thanks!
[0]: https://gcc.gn
ame(type;
I assume you are referring to the child name here?
XXX: We now have functions called AuxiliaryProcessInit() and
InitAuxiliaryProcess(). Confusing.
Based on my analysis, the *Init() is called in the Main functions, while
Init*() is called before the Main functions. Maybe
AuxiliaryProcessInit() could be renamed to AuxiliaryProcessStartup()?
Rename the other to AuxiliaryProcessInit().
--
Tristan Partin
Neon (https://neon.tech)
On Fri Mar 1, 2024 at 8:00 AM CST, Alvaro Herrera wrote:
On 2024-Feb-23, Heikki Linnakangas wrote:
> On 12/02/2024 19:01, Tristan Partin wrote:
> > On Wed Jan 24, 2024 at 8:09 AM CST, Alvaro Herrera wrote:
> > > IMO it would be less ugly to have the origin file lwlocknames.
.
I think with this change, it is unlikely I will be able to upstream
anything to Meson that would benefit Postgres here since setting this
option seems project dependent.
--
Tristan Partin
Neon (https://neon.tech)
ving more automation around include patterns would be great! I think
it would be good if there a Meson run_target()/Make .PHONY target that
people could use to test too. Then, eventually the cfbot could pick this
up.
--
Tristan Partin
Neon (https://neon.tech)
dependencies: [backend_code],
+ include_directories: include_directories('../../../include/storage'),
+ kwargs: internal_lib_args,
+ )
Move the paren to the beginning of the line.
+backend_link_with += lwlock_lib
Earlier in the thread you had said this:
IMO it would be less ugly to have the origin file lwlocknames.txt be
not a text file but a .h with a macro that can be defined by
interested parties so that they can extract what they want from the
file, like PG_CMDTAG or PG_KEYWORD. Using Perl for this seems dirty...
I really like this idea, and would definitely be more inclined to see
a solution like this.
--
Tristan Partin
Neon (https://neon.tech)
On Tue Jan 30, 2024 at 3:58 PM CST, Andres Freund wrote:
Hi,
On 2024-01-30 09:59:25 -0600, Tristan Partin wrote:
> From 331cec1c9db6ff60dcc6d9ba62a9c8be4e5e95ed Mon Sep 17 00:00:00 2001
> From: Tristan Partin
> Date: Mon, 29 Jan 2024 18:03:39 -0600
> Subject: [PATCH v1 1/3] Refuse
On Tue Jan 30, 2024 at 10:00 PM CST, Alexander Lakhin wrote:
Hello,
30.01.2024 18:57, Tristan Partin wrote:
> Patch 1:
>
> Passing NULL as a second argument to memcpy breaks ubsan, ...
Maybe you would like to fix also one more similar place, reached with:
create extension xml
On Tue Jan 30, 2024 at 4:42 PM CST, Jelte Fennema-Nio wrote:
On Tue, 30 Jan 2024 at 23:20, Tristan Partin wrote:
> Not next week, but here is a respin. I've exposed pqSocketPoll as
> PQsocketPoll and am just using that. You can see the diff is so much
> smaller, which is great!
T
On Fri Jan 12, 2024 at 11:13 AM CST, Tristan Partin wrote:
On Fri Jan 12, 2024 at 10:45 AM CST, Robert Haas wrote:
> On Mon, Jan 8, 2024 at 1:03 AM Tristan Partin wrote:
> > I think the way to go is to expose some variation of libpq's
> > pqSocketPoll(), which I would be hap
Spend so much time writing out the email, I once again forget
attachments...UGH.
--
Tristan Partin
Neon (https://neon.tech)
From 331cec1c9db6ff60dcc6d9ba62a9c8be4e5e95ed Mon Sep 17 00:00:00 2001
From: Tristan Partin
Date: Mon, 29 Jan 2024 18:03:39 -0600
Subject: [PATCH v1 1/3] Refuse to
t the Meson build if asan support is requested. That way
others don't spend time heading down a dead end.
--
Tristan Partin
Neon (https://neon.tech)
a look for you. Not sure how hard it will be, but
I can take a crack at it this week.
--
Tristan Partin
Neon (https://neon.tech)
On Fri Jan 26, 2024 at 12:28 AM CST, Peter Eisentraut wrote:
On 25.01.24 17:25, Tristan Partin wrote:
> For what it's worth, I run Meson 1.3, and the behavior of generating the
> tarballs even though it is a dirty tree still occurred. In the new patch
> you seem to say it was
On Thu Jan 25, 2024 at 10:04 AM CST, Peter Eisentraut wrote:
On 22.01.24 21:04, Tristan Partin wrote:
>> + 'HEAD', '.'],
>> + install: false,
>> + output: distdir + '.tar.bz2',
>> +)
>
> The bz2 target should be wrapped i
On Wed Jan 24, 2024 at 10:18 AM CST, Tristan Partin wrote:
On Tue Jan 23, 2024 at 3:30 AM CST, Peter Eisentraut wrote:
> On 22.01.24 21:04, Tristan Partin wrote:
> > I am not really following why we can't use the builtin Meson dist
> > command. The only difference from my t
ering if the issue described in this thread could be related
to the issue I ran into. Afaict the merged patch has not been released
yet.
Do you have a backtrace? Given that the version is 3.2.0, seems likely.
--
Tristan Partin
Neon (https://neon.tech)
On Tue Jan 23, 2024 at 3:30 AM CST, Peter Eisentraut wrote:
On 22.01.24 21:04, Tristan Partin wrote:
> I am not really following why we can't use the builtin Meson dist
> command. The only difference from my testing is it doesn't use a
> --prefix argument.
Here are s
On Tue Jan 23, 2024 at 4:23 PM CST, Andres Freund wrote:
Hi,
On 2024-01-23 15:50:11 -0600, Tristan Partin wrote:
> What is keeping us from using pthread_sigmask(3) instead of sigprocmask(2)?
We would need to make sure to compile with threading support everywhere. One
issue is that on s
On Tue Jan 23, 2024 at 2:10 PM CST, Tristan Partin wrote:
On Tue Jan 23, 2024 at 1:47 PM CST, Andres Freund wrote:
> Hi,
> On 2024-01-23 13:20:15 -0600, Tristan Partin wrote:
> > These checks are not effective for what they are trying to prevent. A recent
> > commit[0] in li
On Tue Jan 23, 2024 at 1:47 PM CST, Andres Freund wrote:
Hi,
On 2024-01-23 13:20:15 -0600, Tristan Partin wrote:
> These checks are not effective for what they are trying to prevent. A recent
> commit[0] in libcurl when used on macOS has been tripping the
> pthread_is_threaded_np()
mit/8b7cbe9decc205b08ec8258eb184c89a33e3084b
[1]:
https://developer.apple.com/documentation/systemconfiguration/1517088-scdynamicstorecopyproxies
--
Tristan Partin
Neon (https://neon.tech)
<>
From 0a514e7a8ea2af21d98cbcc2e4da799745786155 Mon Sep 17 00:00:00 2001
From: Tristan Partin
Date
"meson-ic" way is to use a machine file.
+
+alias_target('pgdist', [check_dirty_index, tar_gz, tar_bz2])
Are you intending for the check_dirty_index target to prohibit the other
two targets from running? Currently that is not the case. If it is what
you intend, use a stamp file or something to indicate a rela
could
install the perltidy file and whatever else too. I keep my Perl writing
to a minimum, so I am not the best person to vouch for these usecases.
[0]:
https://www.postgresql.org/message-id/aaa59ef5-dce8-7369-5cae-487727664127%40dunslane.net
--
Tristan Partin
Neon (https://neon.tech)
On Tue Jan 16, 2024 at 7:27 PM CST, Bruce Momjian wrote:
On Tue, Jan 16, 2024 at 07:22:23PM -0600, Tristan Partin wrote:
> I think a good solution would be to distribute pgindent and pg_bsd_indent.
> At Neon, we are trying to format our extension code using pgindent. I am
> sure there
of us that
pgindent out of tree code. It would also have the added benefit of
adding the tools to $PREFIX/bin, which would make the test that I added
not need a hack to get the pg_bsd_indent executable.
--
Tristan Partin
Neon (https://neon.tech)
From 6e9ca366b6e4976ae591012150fe77729e37c503 Mo
WeoEicnK%3DPCNWEMrA%40mail.gmail.com
[1]:
https://www.postgresql.org/message-id/20220127182838.ba3434dp2pe5vcia%40alap3.anarazel.de
--
Tristan Partin
Neon (https://neon.tech)
From 5ffbc7c35bb3248501b2517d26f99afe02fb53d6 Mon Sep 17 00:00:00 2001
From: Matthias van de Meent
Date: Tue, 27 Jun 2023 15:59:23 +02
On Fri Jan 12, 2024 at 10:45 AM CST, Robert Haas wrote:
On Mon, Jan 8, 2024 at 1:03 AM Tristan Partin wrote:
> I think the way to go is to expose some variation of libpq's
> pqSocketPoll(), which I would be happy to put together a patch for.
> Making frontends, psql in this
t say "run this command line incantation of
pgindent," which in the grand scheme of things is easy compared to all
the other things you have to be aware of to contribute to Postgres.
--
Tristan Partin
Neon (https://neon.tech)
On Tue Jan 9, 2024 at 2:49 PM CST, Robert Haas wrote:
On Tue, Jan 9, 2024 at 2:20 PM Tristan Partin wrote:
> > I don't indent during most of development, and don't intend to start.
>
> Could you expand on why you don't? I could understand as you're writing,
&
change is the culture of Postgres
development. If we can't all agree that we want formatted code, then
there is no point in anything that I discussed.
[0]:
https://marketplace.visualstudio.com/items?itemName=tristan957.postgres-hacker
[1]: https://lists.sr.ht/~rjarry/aerc-devel/patches/48415
--
Tristan Partin
Neon (https://neon.tech)
On Mon Jan 8, 2024 at 6:08 PM CST, Tom Lane wrote:
"Tristan Partin" writes:
> On Mon Jan 8, 2024 at 2:48 PM CST, Tom Lane wrote:
>> +(isascii((unsigned char)
mybuf
hich is what the man page says for these two function, though
isascii(3) explicitly mentions "unsigned char."
Small English nit-pick: I would drop the hyphen between semi and colons.
As for backpatching, seems useful in the sense that people can write the
same script for all supported version of Postgres using the relaxed
syntax.
--
Tristan Partin
Neon (https://neon.tech)
On Sun Dec 31, 2023 at 9:29 PM CST, John Naylor wrote:
On Thu, Dec 28, 2023 at 1:20 AM Tristan Partin wrote:
> I recently wound up in a situation where I was checking for NULL return
> values of a function that couldn't ever return NULL because the
> inability to allocate memory w
On Fri Jan 5, 2024 at 12:24 PM CST, Robert Haas wrote:
On Tue, Dec 5, 2023 at 1:35 PM Tristan Partin wrote:
> On Wed Nov 29, 2023 at 11:48 AM CST, Tristan Partin wrote:
> > I am not completely in love with the code I have written. Lots of
> > conditional compilation which makes
true -- I don't recall any
reports of trouble here -- but it sure looks fragile.
Hence, proposed patch attached.
Looks good to me.
--
Tristan Partin
Neon (https://neon.tech)
On Wed Dec 27, 2023 at 6:42 AM CST, Peter Eisentraut wrote:
On 19.12.23 21:43, Tristan Partin wrote:
> Here is a patch which adds support for the returns_nonnull attribute
> alongside all the other attributes we optionally support.
>
> I recently wound up in a situation where I was
pg_strdup instead which handles it.
Looks good to me.
--
Tristan Partin
Neon (https://neon.tech)
emory was always elog(ERROR)ed (aborted).
I didn't go through and mark anything, but I feel like it could be
useful for people going forward, including myself.
--
Tristan Partin
Neon (https://neon.tech)
From 15a36d68519b332e7ae970708399744cbc69c6c3 Mon Sep 17 00:00:00 2001
From: Tristan Pa
On Tue Dec 19, 2023 at 10:36 AM CST, Jelte Fennema-Nio wrote:
On Mon, 18 Dec 2023 at 22:18, Tristan Partin wrote:
> Here is an additional patch which implements the behavior you described.
> The first patch is just Daniel's squashed version of my patches.
I think we'd still wan
skip the tests as
> appropriate.
Here are patches for these two issues. More testing would be appreciated.
Meson looks good to me!
--
Tristan Partin
Neon (https://neon.tech)
On Mon Dec 18, 2023 at 12:43 AM CST, John Naylor wrote:
On Tue, Dec 5, 2023 at 3:27 AM Tristan Partin wrote:
>
> On Mon Dec 4, 2023 at 2:10 PM CST, Tom Lane wrote:
> > Not sure what you were using, but are you aware that SQL access to the
> > buildfarm database is available
On Mon Dec 18, 2023 at 3:18 PM CST, Tristan Partin wrote:
On Mon Dec 18, 2023 at 10:50 AM CST, Tristan Partin wrote:
> On Mon Dec 18, 2023 at 10:14 AM CST, Jelte Fennema-Nio wrote:
> > On Mon, 18 Dec 2023 at 13:42, Daniel Gustafsson wrote:
> > > I think this is pretty muc
On Mon Dec 18, 2023 at 11:21 AM CST, Jelte Fennema-Nio wrote:
On Mon, 18 Dec 2023 at 17:50, Tristan Partin wrote:
> I could propose something. It would help if I had an example of such
> a tool that already exists.
Basically the same behaviour as what you're trying to add now for
--
On Mon Dec 18, 2023 at 10:50 AM CST, Tristan Partin wrote:
On Mon Dec 18, 2023 at 10:14 AM CST, Jelte Fennema-Nio wrote:
> On Mon, 18 Dec 2023 at 13:42, Daniel Gustafsson wrote:
> > I think this is pretty much ready to go, the attached v4 squashes the
changes
> > and fixes the
tool that already exists.
--
Tristan Partin
Neon (https://neon.tech)
On Mon Dec 18, 2023 at 7:56 AM CST, Euler Taveira wrote:
On Mon, Dec 18, 2023, at 9:41 AM, Daniel Gustafsson wrote:
> > On 15 Dec 2023, at 16:43, Tristan Partin wrote:
>
> > Here is a v3.
>
> I think this is pretty much ready to go, the attached v4 squashes the changes
On Mon Dec 18, 2023 at 6:41 AM CST, Daniel Gustafsson wrote:
> On 15 Dec 2023, at 16:43, Tristan Partin wrote:
> Here is a v3.
I think this is pretty much ready to go, the attached v4 squashes the changes
and fixes the man-page which also needed an update. The referenced Wiki page
wil
fy usage,
and reduce the possibility for version-skew errors.
Seems like you would be forcing an extension author to keep a Postgres
source tree around if you went this route. Perhaps supporting either the
build tree or an install tree would get you the best of both worlds.
--
Tristan Parti
arm avoids this by specifying
# --libdir=lib to meson setup.)
Should we just default the Meson build to libdir=lib in
project(default_options:)? This assumes that you don't think what Tom
said about running it on the build tree is better.
--
Tristan Partin
Neon (https://neon.tech)
1 - 100 of 285 matches
Mail list logo
