]
> https://www.postgresql.org/message-id/flat/CACG%3DezZe1NQSCnfHOr78AtAZxJZeCvxrts0ygrxYwe%3DpyyjVWA%40mail.gmail.com
>
Here's the moderation reason for that message:
Message to list pgsql-hackers held for moderation due to 'Size 1MB (1061796
bytes) is larger than threshold 1000KB (1024000
at least for authorized commitfest members?
> Thanks!
>
The mail system doesn't have the capability to apply different moderation
rules for people in that way I'm afraid.
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
ssage across to the sysadmin team anyway; I can't just change
that setting without buy-in from the rest of the team.
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
On Sun, 20 Mar 2022 at 13:52, Andrew Dunstan wrote:
>
> On 3/19/22 14:48, Andres Freund wrote:
> > Hi,
> >
> > On 2022-03-03 13:37:35 +, Dave Page wrote:
> >> On Thu, 3 Mar 2022 at 13:28, Pavel Borisov
> wrote:
> >>
> >>> The m
hould also
work) fixes the issue.
I'm not sure there's much we can do about this - systems that are likely to
be affected are already out there, and we obviously don't want to relax the
permissions Postgres requires.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: http://www.enterprisedb.com
On Mon, Nov 16, 2020 at 3:55 PM Jonathan S. Katz
wrote:
> On 11/16/20 4:27 AM, Dave Page wrote:
> > Hi,
> >
> > This is more of a head-ups than anything else, as I suspect this may
> > come up in various forums.
> >
> > The PostgreSQL installers f
IMO.
>
It is in the user's homedir - it's just that that isn't under /Users:
hal:~ postgres$ echo $HOME
/Library/PostgreSQL/13
With the EDB installers (unlike postgres.app), PostgreSQL runs as a
service, much as it would on Linux or BSD.
--
Dave Page
Blog: http://pgsn
FYI, both Jonathan and I have now tested this on additional machines and
have been unable to reproduce the issue, so it seems like something odd
happened on my original upgrade rather than a general issue.
Apologies for the noise.
On Mon, Nov 16, 2020 at 9:27 AM Dave Page wrote:
> Hi,
>
Hi
On Tue, Jan 11, 2022 at 12:04 AM Jacob Champion
wrote:
> On Wed, Apr 14, 2021 at 8:42 AM Dave Page wrote:
> > Attached is a patch to clean this up. It will log denials as such
> > regardless of whether or not either selinux or sepgsql is in
> > permissive mode. When ei
thing,
> it'd remove doubt about whether one is looking at a log from a sepgsql
> version that logs this or one that doesn't.
>
> Other than that nitpick, I think we should just push this.
>
Here's an update that adds the "permissive=0" case.
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
sepgsql_permissive_logging_v2.diff
Description: Binary data
t the point of what I was
trying to do, such a message would have indicated to me that I was in
permissive mode without realising.
It seems to me that sepgsql should also log the denial, but flag that
permissive mode is on.
Any reason not to do that?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: http://www.enterprisedb.com
On Thu, Apr 1, 2021 at 3:23 PM Tom Lane wrote:
> Andrew Dunstan writes:
> > On 4/1/21 8:32 AM, Dave Page wrote:
> >> It seems to me that sepgsql should also log the denial, but flag that
> >> permissive mode is on.
>
> > +1 for doing what selinux does if pos
mls=# CREATE TABLE public.tb_users(uid int primary key, name text, mail
text, address text, salt text, phash text);
CREATE TABLE
mls=# drop table tb_users;
ERROR: table "tb_users" does not exist
mls=# drop table public.tb_users;
DROP TABLE
This is on head, pulled yester
ment, or a
value to indicate what the current statement number in the query is?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: http://www.enterprisedb.com
On Mon, Jul 27, 2020 at 4:28 PM Jeremy Schneider
wrote:
> On 7/27/20 07:57, Dave Page wrote:
>
> I'm not sure I'd want that to happen, as it could make it much harder to
> track the activity back to a query in the application layer or server logs.
>
> Perhaps a separ
rade, major or minor.
I would really like to find an acceptable solution to this however as it
really would be good to be able to update ICU.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: http://www.enterprisedb.com
On Tue, Aug 4, 2020 at 10:29 AM Magnus Hagander wrote:
> On Tue, Aug 4, 2020 at 10:07 AM Dave Page wrote:
>
>>
>>
>> On Tue, Aug 4, 2020 at 1:04 AM Bruce Momjian wrote:
>>
>>> On Mon, Aug 3, 2020 at 08:56:06PM +0200, Daniel Verite wrote:
>>> &g
On Mon, Aug 17, 2020 at 11:19 AM Magnus Hagander
wrote:
>
>
> On Fri, Aug 14, 2020 at 3:00 PM Bruce Momjian wrote:
>
>> On Tue, Aug 11, 2020 at 02:58:30PM +0200, Magnus Hagander wrote:
>> > On Tue, Aug 4, 2020 at 11:42 AM Dave Page wrote:
>> > That would
On Mon, Aug 17, 2020 at 4:14 PM Magnus Hagander wrote:
>
>
> On Mon, Aug 17, 2020 at 1:44 PM Dave Page wrote:
>
>>
>>
>> On Mon, Aug 17, 2020 at 11:19 AM Magnus Hagander
>> wrote:
>>
>>>
>>>
>>> On Fri, Aug 14, 2020 at 3:00
On Mon, Aug 17, 2020 at 7:23 PM Bruce Momjian wrote:
> On Mon, Aug 17, 2020 at 04:55:13PM +0100, Dave Page wrote:
> > That was more if the installer actually handles the whole chain. It
> clearly
> > doesn't today (since it doesn't support upgrades), I agree t
rs are in $self->{options}->{gss} .
'\inc\krb5', however in at least the latest installer from MIT they're
actually in $self->{options}->{gss} . '\include'.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: http://www.enterprisedb.com
On Tue, Sep 1, 2020 at 4:22 PM Dave Page wrote:
> I was experimenting with building with MIT Kerberos support on 64 bit
> Windows using MSVC and ran into a number of linker errors along the lines
> of:
>
> "C:\Users\dpage\Downloads\postgresql-12.4\pgsql.sln" (default tar
Hi
On Tue, Sep 1, 2020 at 5:29 PM Stephen Frost wrote:
> Greetings,
>
> * Dave Page (dp...@pgadmin.org) wrote:
> > Attached is a patch against 12.4 for the build system in case anyone
> wants
> > to play (I'll do it properly against the head branch later). I'
Hi
On Wed, Sep 2, 2020 at 9:05 AM Dave Page wrote:
>
>> Yes, that'd be in the GSSENC code, which I hadn't been expecting to be
>> used under Windows.
>
>
Here's a patch to make it build successfully (against head). I believe the
changes to Solution.pm should
On Wed, Sep 2, 2020 at 2:47 PM Stephen Frost wrote:
> Greetings,
>
> * Dave Page (dp...@pgadmin.org) wrote:
> > On Tue, Sep 1, 2020 at 5:29 PM Stephen Frost wrote:
> > > * Dave Page (dp...@pgadmin.org) wrote:
> > > > Attached is a patch against 12.4
Hi
On Wed, Sep 2, 2020 at 7:08 PM Stephen Frost wrote:
> Greetings,
>
> * Dave Page (dp...@pgadmin.org) wrote:
> > On Wed, Sep 2, 2020 at 9:05 AM Dave Page wrote:
> > >> Yes, that'd be in the GSSENC code, which I hadn't been expecting to be
> > >&
On Wed, Sep 2, 2020 at 5:21 PM Dave Page wrote:
>
>
> On Wed, Sep 2, 2020 at 2:47 PM Stephen Frost wrote:
>
>> Greetings,
>>
>> * Dave Page (dp...@pgadmin.org) wrote:
>> > On Tue, Sep 1, 2020 at 5:29 PM Stephen Frost
>> wrote:
>> > > *
On Thu, Sep 3, 2020 at 4:15 PM Dave Page wrote:
>
> So having rebuilt PostgreSQL against that, I'm now in the situation where
> the server never even attempts to get a ticket as far as I can see, and
> psql just crashes with nothing more than a useless error in the event
thod. I think the HIDDEN attribute provide a common and basic way to
> implement that in all client application.
>
I like the idea - being able to hide computed columns such as tsvectors
from CRUD queries by default seems like it would be very nice for example.
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
or PG15. We
build many components aside from PostgreSQL, and need to use the same
toolchain for all of them (we've had very painful experiences with mix n
match CRT versions in the past) so it's not just PG that needs to support
VS2022 as far as we're concerned - Perl, Python
Hi
On Wed, Nov 24, 2021 at 11:36 AM Michael Paquier
wrote:
> On Wed, Nov 24, 2021 at 10:00:19AM +0000, Dave Page wrote:
> > It's extremely unlikely that we'd shift to such a new version for PG15.
> We
> > build many components aside from PostgreSQL, and need to us
so there
are also benefits other than ACID to storing data in this way.
BTW; for pgAdmin related GSoC questions, you'd do better to ask on
pgadmin-hack...@postgresql.org.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Due to circumstances beyond my control, I've had to shut down the ageing
Windows buildfarm animals in $SUBJECT.
I hope to restart them at some point, but it might be some time.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.co
iki.postgresql.org/wiki/FOSDEM/PGDay_2018_Developer_Meeting).
>>
>>
> In the notes there is this, which confused me:
>
>
> > SIDE TOPIC:
> >
> > Release date for PostgreSQL 13 agreed: Friday 13th September 2019!!
>
>
> Isn't Postgres 12 to be released i
sent you an invitation letter, and after you
> join, I am willing to hand over the administrator of the organization to
> you.
>
>
> Regards,
> Hongyuan Ma (cs_maleica...@163.com)
>
>
>
>
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
m the pgAdmin team) that know
those technologies. It is important to consider long term maintenance as
well as ease of initial development with any project.
Thanks.
>
> Regards,
> Hongyuan Ma (cs_maleica...@163.com)
>
> 在 2018-03-12 02:26:43，"Dave Page" 写道：
>
> H
who
have submitted a number of good quality patches (in the case of PostgreSQL
and pgAdmin, that can be over the course of years!). For the perffarm, I
expect the bar to be a little lower than that, but for now you should
assume you'll be sending patches for review.
Thanks.
>
> Best Re
> On 14 Mar 2018, at 19:14, Mark Wong wrote:
>
> Hi,
>
> I have some additional comments to a couple areas...
>
>> On Wed, Mar 14, 2018 at 05:33:00PM -0400, Dave Page wrote:
>>> On Tue, Mar 13, 2018 at 11:31 PM, Hongyuan Ma wrote:
>>> At the same
adminpack 1.0 version completely, the 1.0 functions
> pg_file_read, pg_file_length and pg_logfile_rotate will also go away
> making adminpack code simpler.
>
> Having said that, it's good to hear from others, preferably from
> pgadmin developers - added Dave Page (dp...@pgadmin.org
t :-). We use Sphinx now.
>
> But I have heard less about htmlhelp over the years than about the info
> format.
>
>
>
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
baked into a fully automated build system (even the
build servers and all their requirements are baked into Ansible).
Changing that lot would be non-trivial, though certainly possible, and I
suspect we’re not the only ones doing that sort of thing.
--
--
Dave Page
https://pgsnake.blogspot.com
EDB Postgres
https://www.enterprisedb.com
On Tue, 11 Apr 2023 at 08:09, Magnus Hagander wrote:
> On Tue, Apr 11, 2023 at 12:27 AM Andres Freund wrote:
> >
> > Hi,
> >
> > On 2023-04-10 19:55:35 +0100, Dave Page wrote:
> > > Projects other than the EDB installers use the MSVC build system - e.g.
&
On Tue, 11 Apr 2023 at 11:58, Andrew Dunstan wrote:
>
> On 2023-04-11 Tu 04:05, Dave Page wrote:
>
>
>
> On Tue, 11 Apr 2023 at 08:09, Magnus Hagander wrote:
>
>> On Tue, Apr 11, 2023 at 12:27 AM Andres Freund
>> wrote:
>> >
>> > Hi,
>
On Tue, 11 Apr 2023 at 13:52, Jonathan S. Katz wrote:
> On 4/11/23 7:54 AM, Dave Page wrote:
> >
> >
> > On Tue, 11 Apr 2023 at 11:58, Andrew Dunstan > <mailto:and...@dunslane.net>> wrote:
> >
> > For meson you just need to to "pip install
SVC versions. (That's very
> distinct from how far back we need the built code to run.)
>
> regards, tom lane
>
>
>
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
org
> "https://[$h]/docs/release/14.2/";
> | grep ^HTTP; done
> 2001:4800:3e1:1::230: HTTP/2 200
> 2a02:c0:301:0:::32: HTTP/2 404
> 2a02:16a8:dc51::50: HTTP/2 200
>
Despite the name, they're not actually mirrors. They're varnish cach
bels rather than the metrics themselves
(e.g. server version strings or LSNs). I would much prefer to see a common
format such as JSON used by default, and perhaps offer a hook to allow
alternate formatters to replace that. The prometheus format is also pretty
inefficient, as you have to repeat all the key data (labels) for each
individual metric.
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
at. Cases where it should be
disabled are *extremely* rare. Make sure you *really* know what you're
letting yourself in for by disabling autovacuum, and don't rely on 10+ year
old performance tuning advice from random places on the internet, if that's
what you're doing.
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
5. Thanks for the report,
> Robert. And thanks for the patch, Dave.
>
Thank you!
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
Hi
On Tue, Apr 13, 2021 at 6:22 PM Robert Haas wrote:
> On Tue, Apr 13, 2021 at 10:33 AM Dave Page wrote:
> > On a system with selinux and sepgsql configured, search path resolution
> appears to fail if sepgsql is in enforcing mode, but selinux is in
> permissive mode (which,
Hi
On Thu, Apr 1, 2021 at 3:30 PM Dave Page wrote:
>
>
> On Thu, Apr 1, 2021 at 3:23 PM Tom Lane wrote:
>
>> Andrew Dunstan writes:
>> > On 4/1/21 8:32 AM, Dave Page wrote:
>> >> It seems to me that sepgsql should also log the denial, but flag that
>
version
-
PostgreSQL 12.6 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu
5.4.0-6ubuntu1~16.04.12) 5.4.0 20160609, 64-bit
(1 row)
So I guess it's a case of "it dep
ns the gss_krb5_ccache_name call is not made and the
> current behaviour (of letting the GSSAPI library work out the location
> of the ccache) is not changed.
>
> Many thanks,
> Daniel
>
>
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
can't currently see an obvious way to get this kind of setup working
> using only the environment variable.
>
> Many thanks,
> Daniel
>
>
>
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
at precise use case upthread. As you know, we've been
adding Kerberos support to pgAdmin. When running in server mode, we have
multiple users logging into a single instance of the application, and we
need to cache credentials for them to be used to login to the PostgreSQL
servers, using libpq that is on the pgAdmin server. For obvious reasons, we
want to use separate credential caches for each pgAdmin user, and currently
that means having a mutex around every use of the caches, so we can be sure
we're safely manipulating the environment, using the correct cache, and
then continuing as normal once we're done.
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
, which is
synonymous with MACOSX_DEPLOYMENT_TARGET. We've been successfully building
packages that way for a decade or more.
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
Hi
On Fri, 30 Sept 2022 at 18:58, Andres Freund wrote:
> Hi,
>
> On 2022-09-30 17:58:31 +0200, Vik Fearing wrote:
> > On 9/7/22 12:03, Dave Page wrote:
> > > Here's a v4 patch. This reverts to using
> > > GetCurrentTransactionStopTimestamp() for t
On Wed, 12 Oct 2022 at 07:40, Michael Paquier wrote:
> On Mon, Oct 03, 2022 at 12:55:40PM +0100, Dave Page wrote:
> > Thanks. It's just the changes in xact.c, so it doesn't seem like it would
> > cause you any more work either way, in which case, I'll leave it to y
is passed in.
>
Thanks for that. It looks good to me, bar one comment (repeated 3 times in
the sql and expected files):
fetch timestamps from before the next test
"from " should be removed.
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
On Fri, 14 Oct 2022 at 19:16, Andres Freund wrote:
> Hi,
>
> On 2022-10-13 14:38:06 +0100, Dave Page wrote:
> > Thanks for that. It looks good to me, bar one comment (repeated 3 times
> in
> > the sql and expected files):
> >
> > fetch timestamps from before
FYI, this is not intentional, and I do plan to look into it, however I've
been somewhat busy with pgconfeu, and am travelling for the rest of this
week as well.
On Sun, 23 Oct 2022 at 21:09, Robert Treat wrote:
> On Fri, Oct 14, 2022 at 2:55 PM Dave Page wrote:
> > On Fri, 14 Oct
On Mon, 31 Oct 2022 at 07:36, Dave Page wrote:
> FYI, this is not intentional, and I do plan to look into it, however I've
> been somewhat busy with pgconfeu, and am travelling for the rest of this
> week as well.
>
Here's a patch to fix this issue. Many thanks to Peter
a FSM", "a FIFO", "a SSPI", "a SASL", "a MCV", "a SHA", "a SQLDA"
> >
> > My regex foo is not strong enough to think how I might find multiline
> instances.
>
> Um, of those, I pronounce FIFO, SASL, and SHA as words, with an "a"
> article.
>
Same here. I've never heard anyone try to pronounce SSPI, so I would expect
that to be "an SSPI ...". The other remaining ones (FSM, MCV & SQLDA) I
would also argue aren't pronounceable, so should use the "an" article.
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
the server didn't find my
> public key, but the fingerprint shown above coincides with that of the
> registered public key. I don't have a clue of the reason from my side.
>
> Please someone tell me what to do to get over the situation.
>
> regards.
>
> --
> Kyotaro Horiguchi
> NTT Open Source Software Center
>
>
>
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
Hi
On Wed, 11 May 2022 at 08:55, Kyotaro Horiguchi
wrote:
> At Wed, 11 May 2022 08:46:40 +0100, Dave Page wrote
> in
> > Hi
> >
> > On Wed, 11 May 2022 at 08:21, Kyotaro Horiguchi >
> > wrote:
> > > 2. Clone ssh://g...@gitmaster.postgresql.org/pgtran
lon:~#
>
>
> Also Tom Lane said:
> On Sun, May 1, 2022 at 4:52 PM Tom Lane wrote:
> > Tatsuo Ishii writes:
> > > This is ok:
> > > git clone ssh://g...@gitmaster.postgresql.org/postgresql.git
> >
> > That's the thing to use if you're a committer.
>
> Best reagards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
>
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
On Wed, 11 May 2022 at 09:25, Kyotaro Horiguchi
wrote:
> At Wed, 11 May 2022 09:08:26 +0100, Dave Page wrote
> in
> > What is your community user ID?
>
> My community user name is "horiguti".
>
OK, so you have write access on the repo on git.postgresql.org, but I
2020 mhatest.git
> > drwxr-sr-x 7 git git 4096 May 11 06:39 postgresql.git
> > gemulon:~#
>
> Sorry, I meant ssh://g...@gitmaster.postgresql.org/postgresql.git
> works, but ssh://g...@git.postgresql.org/postgresql.git does not work
> for me.
>
That is expected; no one has
) someone has been confused by gitmaster
recently, something both Magnus and I have been surprised by.
--
--
Dave Page
https://pgsnake.blogspot.com
EDB Postgres
https://www.enterprisedb.com
yourself. Anyone else can
*only* use git.postgresql.org
>
> BTW,
> > I'm going to try a slightly different steps..
>
> Can you please tell me What you actually did? I am afraid of facing
> similar problem if I want to add another committer to pgpool2 repo.
>
> Best
gt;
So we just ran into this whilst updating pgAdmin to support PG15. How is
one supposed to figure out what the last system OID is now from an
arbitrary database? pgAdmin uses that value in well over 300 places in its
source.
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitt
On Mon, 16 May 2022 at 15:06, David Steele wrote:
> On 5/16/22 9:43 AM, Dave Page wrote:
> >
> >
> > On Thu, 20 Jan 2022 at 14:03, Robert Haas > <mailto:robertmh...@gmail.com>> wrote:
> >
> > On Mon, Jan 17, 2022 at 3:43 PM Tom Lane > &
k hack to get pldebugger to load into
> v15/HEAD. It lacks #ifdef's which'd be needed so that it'd still
> compile against older branches, but perhaps this'll save someone
> some time.
>
Thanks Tom - I've pushed that patch with the relevant #ifdefs added.
--
Dave Page
PostgreSQL Core Team
http://www.postgresql.org/
it is any good.
>
I agree. This is an area in which there are lots of options at the moment,
with compelling reasons to choose from various of them depending on your
needs.
It's this kind of choice that means it's unlikely we'd include any one
option in PostgreSQL, much like various other tools such as failover
managers or poolers.
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
EDB: https://www.enterprisedb.com
cludes. I changed the comment a little to make it understandable.
> I am also attaching the error generated with ninja build.
>
> OR
>
> 2). Right after the gssapi includes in libpq-be.h
>
Thank you for working on this. I can confirm the undef version compiles and
passes tests w
On Tue, 11 Jun 2024 at 12:22, Andrew Dunstan wrote:
>
> On 2024-06-11 Tu 05:19, Dave Page wrote:
>
> Hi
>
> On Sun, 9 Jun 2024 at 08:29, Imran Zaheer wrote:
>
>> Hi
>>
>> I am submitting two new patches. We can undefine the macro at two
>> locations
57ue8rmhq6CD1Jic5uqKh80=vtpzurskesn-...@mail.gmail.com
[2] https://github.com/dpage/winpgbuild/actions
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
EDB: https://www.enterprisedb.com
Hi
On Tue, 18 Jun 2024 at 15:38, Andres Freund wrote:
> Hi,
>
> On 2024-06-18 14:53:53 +0100, Dave Page wrote:
> > My next task was to extend that to support PostgreSQL 17 and beyond,
> which
> > is where I started to run into problems. I've attempted builds using
to
> add fragile stuff that will barely be tested, when not necessary.
>
> Greetings,
>
> Andres Freund
>
>
> [1] Here's a build of PG with the dependencies installed, builds
> https://cirrus-ci.com/task/4953968097361920
>
> [2] E.g.
>
> http
It's making many of those changes for non-Windows
platforms as well.
>
> -
> https://github.com/conda-forge/postgresql-feedstock/tree/main/recipe/patches
That one is interesting. It fixes the same zlib and OpenSSL issues I
mentioned being the one fix I did myself, albeit by renaming libraries
originally, and later by actually following the upstream build instructions
correctly.
It also makes essentially the same fix for krb5 that I hacked into my
Github Action, but similarly that isn't actually needed at all if you
follow the documented krb5 build process, which produces 32 and 64 bit
binaries.
Additionally, it also fixes a GSSAPI related bug which I reported a week or
two back here and for which there is a patch waiting to be committed, and
replaces some setenv calls with _putenv_.
There are a couple more patches in there, but they're Linux related from a
quick glance.
In short, I don't really see anything in those examples that are general
issues (aside from the bugs of course).
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
EDB: https://www.enterprisedb.com
Hi
On Fri, 21 Jun 2024 at 12:20, Dave Page wrote:
>
> We/I *could* add cmake/pc file generation to that tool, which would make
> things work nicely with PostgreSQL 17 of course.
>
For giggles, I took a crack at doing that, manually creating .pc files for
everything I've bee
On Fri, 21 Jun 2024 at 16:15, Robert Haas wrote:
> On Fri, Jun 21, 2024 at 7:21 AM Dave Page wrote:
> > My assumption all along was that Meson would replace autoconf etc.
> before anything happened with MSVC, precisely because that's the type of
> environment all the P
is not
trivial to setup. That's largely why I started working on
https://github.com/dpage/winpgbuild.
Thanks!
>
> Happy to hear your thoughts. I think if our goal is to enable more
> people to work on Postgres, we should probably add subproject wraps to
> the source tree, but we also need to be forgiving like in the Meson DSL
> snippet above.
>
> Let me know your 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
>
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
EDB: https://www.enterprisedb.com
it on
> windows. On other platforms it'd be quite inadvisable to statically link
> libraries, due to security updates, but for stuff like the EDB windows
> installer dynamic linking doesn't really help with that afaict?
>
Correct - we're shipping the dependencies ourselves, so we have to
rewrap/retest anyway.
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
EDB: https://www.enterprisedb.com
On Sat, 22 Jun 2024 at 17:35, Andres Freund wrote:
> Hi,
>
> On 2024-06-21 15:36:56 +0100, Dave Page wrote:
> > For giggles, I took a crack at doing that, manually creating .pc files
> for
> > everything I've been working with so far.
>
> Cool!
>
>
>
On Tue, 25 Jun 2024 at 11:41, Andres Freund wrote:
> Hi,
>
> On 2024-06-21 12:20:49 +0100, Dave Page wrote:
> > > I'm confused - the old build system wasn't flexible around this stuff
> *at
> > > all*. Everyone had to patch it to get dependencies to work,
Hi
On Tue, 25 Jun 2024 at 12:39, Andres Freund wrote:
> Hi,
>
> On 2024-06-25 11:54:56 +0100, Dave Page wrote:
> > https://github.com/dpage/winpgbuild proves that the hacks above are not
> > required *if* you build the dependencies in the recommended way for use
&
I can't speak for others of course, but at least as far as building of
installers is concerned, we use tarballs not git checkouts.
For my own work; well, I've started playing with PG17 on Windows just in
the last month or so and have noticed a number of test failures as well as
a weird meson issue that only shows up on a Github actions runner. I was
hoping to look into those issues this week as I've been somewhat
sidetracked with other work of late.
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
EDB: https://www.enterprisedb.com
rt for it in older branches.
Packagers aren't likely to be using readline, as it's GPL and it would have
to be shipped with packages on Windows. They are more likely to be using
libedit if anything. Not sure if that has any bearing on the compilation
failure.
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
EDB: https://www.enterprisedb.com
/027_nosuperuser
ERROR 102.02s exit status 2
269/298 postgresql:subscription / subscription/031_column_list
ERROR 123.16s exit status 2
271/298 postgresql:subscription / subscription/032_subscribe_use_index
ERROR 139.33s exit status 2
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
EDB: https://www.enterprisedb.com
On Tue, 9 Jul 2024 at 17:32, Andres Freund wrote:
> Hi,
>
> On 2024-07-09 14:52:39 +0100, Dave Page wrote:
> > I have 4 different diff.exe's on my ~6 week old build VM (not counting
> > shims), all of which seem to support --strip-trailing-cr. Those builds
> came
>
Sorry - somehow managed to send whilst pasting in logs...
On Wed, 10 Jul 2024 at 10:30, Dave Page wrote:
>
>
> On Tue, 9 Jul 2024 at 17:32, Andres Freund wrote:
>
>> Hi,
>>
>> On 2024-07-09 14:52:39 +0100, Dave Page wrote:
>> > I have 4 different dif
On Tue, 9 Jul 2024 at 17:23, Andres Freund wrote:
> Hi,
>
> On 2024-07-09 09:14:33 +0100, Dave Page wrote:
> > On Mon, 8 Jul 2024 at 21:08, Andres Freund wrote:
> > > I think we'd need to backpatch more for older branches. At least
> > >
> > >
On Wed, 10 Jul 2024 at 12:12, Andrew Dunstan wrote:
>
> On 2024-07-09 Tu 11:34 AM, Andrew Dunstan wrote:
>
>
> On 2024-07-09 Tu 9:52 AM, Dave Page wrote:
>
>
>
>> > What I suggest (see attached) is we run the diff command with
>> > --strip-trailing-cr
On Wed, 10 Jul 2024 at 10:35, Dave Page wrote:
> > The other failures I see are the following, which I'm just starting to
>>> dig
>>> > into:
>>> >
>>> > 26/298 postgresql:recovery / recovery/019_replslot_limit
>>> &g
g I will note is that PG16 and earlier try to use the wrong
filename for the import library. For years, it's been a requirement to do
something like this: "copy \zlib\lib\zlib.lib \zlib\lib\zdll.lib" to make a
build succeed against a "vanilla" zlib build. I haven't go
Hi
On Tue, 21 May 2024 at 15:12, Sandeep Thakkar <
sandeep.thak...@enterprisedb.com> wrote:
> Hi Dave,
>
>
> On Tue, May 21, 2024 at 3:12 PM Dave Page wrote:
>
>> Hi Sandeep, Nazir,
>>
>> On Tue, 21 May 2024 at 10:14, Nazir Bilal Yavuz
>> wrote:
&g
On Tue, 21 May 2024 at 16:04, Andres Freund wrote:
> Hi,
>
> On 2024-05-20 11:58:05 +0100, Dave Page wrote:
> > I have very little experience with Meson, and even less interpreting it's
> > logs, but it seems to me that it's not including the extra lib and
> in
On Tue, 21 May 2024 at 18:00, Andres Freund wrote:
> Hi,
>
> On 2024-05-20 11:58:05 +0100, Dave Page wrote:
> > I then attempt to build PostgreSQL:
> >
> > meson setup build
> > -Dextra_include_dirs=C:/build64/openssl/include,C:/build64/zlib/include
> > -D
On Tue, 21 May 2024 at 20:54, Andrew Dunstan wrote:
>
> On 2024-05-21 Tu 11:04, Andres Freund wrote:
> > Hi,
> >
> > On 2024-05-20 11:58:05 +0100, Dave Page wrote:
> >> I have very little experience with Meson, and even less interpreting
> it's
&g
1 - 100 of 146 matches
Mail list logo
