Hi
On Wed, 22 May 2024 at 14:11, Nazir Bilal Yavuz wrote:
> Hi,
>
> On Tue, 21 May 2024 at 18:24, Dave Page wrote:
> >
> >
> >
> > On Tue, 21 May 2024 at 16:04, Andres Freund wrote:
> >>
> >> Hi,
> >>
> >> On 2024-05-20
On Wed, 22 May 2024 at 17:50, Nazir Bilal Yavuz wrote:
> Hi,
>
> On Wed, 22 May 2024 at 17:21, Dave Page wrote:
> >
> > Hi
> >
> > On Wed, 22 May 2024 at 14:11, Nazir Bilal Yavuz
> wrote:
> >>
> >>
> >> I tried to install your late
: error C2449: found
'{' at file scope (missing function header?)
[C:\Users\dpage\Downloads\postgresql-16.3
\postgres.vcxproj]
C:\build64\openssl\include\openssl\x509v3.h(527,1): error C2059: syntax
error: '}' [C:\Users\dpage\Downloads\postgresql-16.3\postgres.vcxproj]
C:\build64\openssl\include\openssl\x509v3.h(527,1): error C2146: syntax
error: missing ')' before identifier 'fr'
[C:\Users\dpage\Downloads\postgresql-16.3\p
ostgres.vcxproj]
C:\build64\openssl\include\openssl\x509v3.h(527,1): error C2061: syntax
error: identifier 'fr'
[C:\Users\dpage\Downloads\postgresql-16.3\postgres.vcxproj]
C:\build64\openssl\include\openssl\x509v3.h(527,1): error C1003: error
count exceeds 100; stopping compilation
[C:\Users\dpage\Downloads\postgresql-16.3\post
gres.vcxproj]
4 Warning(s)
53 Error(s)
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
EDB: https://www.enterprisedb.com
d
have objected loudly). Having recently started testing Meson on Windows
when I realised that change had been made, and having to update builds for
pgAdmin and the Windows installers, I think it's clear it's far more
experimental on that platform than it is on Linux at least.
--
Da
Hi
On Tue, 4 Jun 2024 at 17:36, Heikki Linnakangas wrote:
> On 04/06/2024 18:28, Dave Page wrote:
> > I clearly missed the discussion in which it was decided to remove the
> > old MSVC++ support from the tree (and am disappointed about that as I
> > would have objected lou
2.05343896
Doc and test updates included.
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
last_scan_v1.diff
Description: Binary data
Hi
On Tue, 23 Aug 2022 at 13:07, Greg Stark wrote:
> On Tue, 23 Aug 2022 at 11:00, Dave Page wrote:
> >
> > Often it is beneficial to review one's schema with a view to removing
> indexes (and sometimes tables) that are no longer required. It's very
> difficult
On Wed, 24 Aug 2022 at 15:18, Bruce Momjian wrote:
> On Tue, Aug 23, 2022 at 10:55:09AM +0100, Dave Page wrote:
> > Often it is beneficial to review one's schema with a view to removing
> indexes
> > (and sometimes tables) that are no longer required. It's very diffic
On Wed, 24 Aug 2022 at 16:03, Bruce Momjian wrote:
> On Wed, Aug 24, 2022 at 04:01:21PM +0100, Dave Page wrote:
> > On Wed, 24 Aug 2022 at 15:18, Bruce Momjian wrote:
> >
> > On Tue, Aug 23, 2022 at 10:55:09AM +0100, Dave Page wrote:
> > > Often it is ben
Hi
On Thu, 25 Aug 2022 at 01:44, David Rowley wrote:
> On Thu, 25 Aug 2022 at 03:03, Bruce Momjian wrote:
> >
> > On Wed, Aug 24, 2022 at 04:01:21PM +0100, Dave Page wrote:
> > > On Wed, 24 Aug 2022 at 15:18, Bruce Momjian wrote:
> > > Would it be simpler
On Tue, 30 Aug 2022 at 19:46, Bruce Momjian wrote:
> On Fri, Aug 26, 2022 at 02:05:36PM +0100, Dave Page wrote:
> > On Thu, 25 Aug 2022 at 01:44, David Rowley wrote:
> > I don't have a particular opinion about the patch, I'm just pointing
> > out that
On Wed, 31 Aug 2022 at 17:13, Bruce Momjian wrote:
> On Wed, Aug 31, 2022 at 05:02:33PM +0100, Dave Page wrote:
> >
> >
> > On Tue, 30 Aug 2022 at 19:46, Bruce Momjian wrote:
> >
> > On Fri, Aug 26, 2022 at 02:05:36PM +0100, Dave Page wrote:
> >
On Thu, 1 Sept 2022 at 13:04, Bruce Momjian wrote:
> On Thu, Sep 1, 2022 at 09:46:59AM +0100, Dave Page wrote:
> > On Wed, 31 Aug 2022 at 17:13, Bruce Momjian wrote:
> > Wow. I was just thinking you need second-level accuracy, which must
> be
> > cheap somew
notes, is likely to lose 95% of users.
Updated patch attached:
- GUC removed.
- The timestamp recorded is xactStartTimestamp.
- Docs updated to make it clear we're recording transaction start time.
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
last_scan_v3.diff
Description: Binary data
Hi
On Tue, 6 Sept 2022 at 16:53, Andres Freund wrote:
> Hi,
>
> On 2022-09-06 14:15:56 +0100, Dave Page wrote:
> > Vik and I looked at this a little, and found that we actually don't have
> > generally have GetCurrentTransactionStopTimestamp() at this point - a
onal pkgconfig file needed
for ICU now, so it should better match a *nix build.
Any chance you can look at the GSSAPI/OpenSSL X509_NAME conflict one? I'm
still having to patch around that to build with all the dependencies.
https://www.postgresql.org/message-id/flat/CA%2BOCxoxwsgi8QdzN8A0OPGuGfu
Hi
On Sat, 13 Jul 2024 at 23:01, Thomas Munro wrote:
> On Fri, Jul 12, 2024 at 3:49 AM Dave Page wrote:
> > So I received an off-list tip to checkout [1], a discussion around
> GSSAPI causing test failures on windows that Alexander Lakhin was looking
> at. Thomas Munro'
Joe replied.
I've just checked again myself and I don't see any problems with the sites
mentioned from a user perspective, but there are some non-obvious issues
being reported by Nagios on git.postgresql.org (which is not the same as
gitmaster). We'll dig in some more.
--
Dave
ts: 100% (42814/42814), done.
remote: Compressing objects: 100% (15585/15585), done.
remote: Total 1014138 (delta 34190), reused 33980 (delta 26978),
pack-reused 971324
Receiving objects: 100% (1014138/1014138), 343.01 MiB | 15.49 MiB/s, done.
Resolving deltas: 100% (873517/873517), done.
--
ight at the moment,
>
> https://git.postgresql.org/gitweb/?p=postgresql.git
>
> is failing for me with "Backend fetch failed".
That's working fine for me now, however Magnus did just give the box some
more CPUs.
We're also considering rate limiting by IP on that se
, especially
those that support side-by-side installations of different versions. None
of ours (EDBs) will be doing so.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
xisting binary names.
I think the beauty of having a single CLI executable is that we can
redesign the user interface to make it nice and consistent for all the
different functions it offers, and to cleanup old cruft such as createuser
vs. createrole and pgbench vs. pg_* and so on.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
'd like to get rid of it, we don't have an alternative for
Windows do we? The docs for 11 imply it's required for UUID support
(though the wording isn't exactly clear, saying it's required for
UUID-OSSP support!):
https://www.postgresql.org/docs/11/install-windows-full.html#id
> On 12 Feb 2019, at 16:00, Greg Stark wrote:
>
> I was just perusing our PDF docs for the first time in ages and
> realized that of the 3,400+ pages of docs there's about 1,000 pages of
> release notes in it That seems like a bit overkill.
>
> I love having the old release notes online b
https://developer.apple.com/documentation/security/hardened_runtime and
https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_security_cs_allow-jit
We're working on trying to test a patch for that at the moment.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
to the admin site to do this and got a 500
error. Unfortunately I'm now off to take a number of meetings, so can't
look more closely myself.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
> I certainly like the (future) patent holder coming forth to offer a
> > grant a lot better than the one who doesn't (but still holds the
> > patent). I'm missing the appreciation for that former strategy in this
> > thread and fear we're setting a
On Wed, Jul 11, 2018 at 1:34 AM, Tsunakawa, Takayuki <
tsunakawa.ta...@jp.fujitsu.com> wrote:
> From: Dave Page [mailto:dp...@pgadmin.org]
> > SFLC have acted as the projects counsel in the past, so I'm not surprised
> > they aren't talking to you; you won'
have no idea of
the benefit of, that if posted now would likely not get any eyes on them at
all precisely because they're covered by a patent.
tldr; it's a crap ton of work, risk and uncertainty for what might well be
zero benefit at the moment.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Tue, Jul 24, 2018 at 4:26 PM, Tomas Vondra
wrote:
> On 07/24/2018 05:20 PM, Alvaro Herrera wrote:
>
>> On 2018-Jul-24, Dave Page wrote:
>>
>> tldr; it's a crap ton of work, risk and uncertainty for what might well be
>>> zero benefit at the moment.
>&g
tgresql.git'. I don't know what is the
> issue.
>
It worked for me with https. Can you try again? It may be that the Varnish
cache was doing it's meditation thing for some reason. I can't see anything
obvious on the system though - nothing in the logs, and the services have
all been up for days.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: http://www.enterprisedb.com
ecks ? Am I missing
> something ?
>
> This is the mailinglist for the core postgres database server. While there
> certainly are lots of people skilled in pgadmin here, you will probably
> have a
> better chance of getting help on the pgadmin-support mailinglist:
>
> h
g community
user account system and our underlying infrastructure. Don't expect a nice
shiny RPM or DEB that you can just install and run - it would almost
certainly take a fair amount of effort.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
browser) and use to unsubscribe yourself
>> from this list.
>>
>> The changes which we expect to be most significant to users can be found
>> on the wiki here: https://wiki.postgresql.org/wiki/PGLister_Announce the
>> current version of which is also included below.
>>
>
I've certainly heard of cases where pg_upgrade takes significant amounts of
time to run on very complex databases.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
are assholes. We're not agreeing to join
> some organization and sign an ethics clause when signing up for the mailing
> list. The current moderators can already remove bad actors from the list.
> How they act outside of the list is non of this list's concern.
>
n the reddis community right now
>> we can see conversations spilling onto twitter and into ad hominem
>> vitriol.
>>
>
> Ask yourself, if this was a government agency tracking your speech across
> platforms would you be as approving? Personally I find the whole thing
> creepy.
No one is tracking anything as part of the CoC. That's nothing but a straw
man argument.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
specific
> agreements to the contrary, why should any one group claim responsibility
> of my
> personal business?
>
If that business is publicly bringing the project into disrepute, or
harassing other community members and they approach us about it, then it
becomes our business.
If it's unrelated to PostgreSQL, then it's your personal business and not
something the project would get involved in.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
at they become abusive
or offensive to people making other software choices, then they are clearly
bringing the project into disrepute and we should have every right to
sanction them by preventing them participating in our project in whatever
ways are deemed appropriate.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Fri, Sep 14, 2018 at 3:37 PM, Joshua D. Drake
wrote:
> On 09/14/2018 07:14 AM, Dave Page wrote:
>
>
>
> On Fri, Sep 14, 2018 at 3:08 PM, Joshua D. Drake
> wrote:
>
>> On 09/14/2018 01:31 AM, Chris Travers wrote:
>>
>>
>> I apologize for the
nteract.
>>
>>
>> I could only heavily +1 this. I can get from where comes the idea that
>> community is only what happens just on postgresql.org or just on some
>> other channel community uses. Community is people who joined it and CoC
>> supposed to apply even if peopl
On Fri, Sep 14, 2018 at 3:43 PM, Joshua D. Drake
wrote:
> On 09/14/2018 07:36 AM, Dave Page wrote:
>
>
>
> On Fri, Sep 14, 2018 at 3:21 PM, James Keener wrote:
>
>>
>> Now, you may say that (2) would be rejected by the committee, but I would
>>>>
g down
> the rest of the groups throats.
>
> Jim
>
> PS: Also, what's with the personal replies? If you don't want to say what
> you want to the whole group, I don't really have an interest in talking to
> you personally.
>
I've had one off-list per
ere will always be people who don't
like some of the wording, much as there are often people who disagree with
the way a patch to the code is written. Sooner or later though, the general
consensus prevails and we have to move on, otherwise nothing will ever get
completed.
--
Dave Page
Blog
On Fri, Sep 14, 2018 at 3:28 PM, Adrian Klaver
wrote:
> On 9/14/18 7:19 AM, Dave Page wrote:
>
>>
>>
>>
>
>> No one is tracking anything as part of the CoC. That's nothing but a
>> straw man argument.
>>
>
> Not buying it or the belo
We would like to extend our thanks and gratitude to Stacey Haysler for her
patience and expertise in helping develop the Code of Conduct, forming the
committee and guiding the work to completion.
--
Dave Page
PostgreSQL Core Team
http://www.postgresql.org/
<http://www.postgresql.org/>
I got a complaint today that pg_regress.exe is no longer
part of the Windows installation footprint - and indeed, it's not installed
at all with Meson builds, which is problematic for those doing CI/CD
testing of extensions.
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
On Sun, 27 Oct 2024 at 10:17, 黄铎彦 <00...@fzu.edu.cn> wrote:
> I could hardly find detailed and complete tutorials on building the latest
> version with Visual Studio.
>
You can see how it’s done if you take a look at the actions in
https://github.com/dpage/winpgbuild. The postgresql-dev one i
On Mon, 11 Nov 2024 at 15:35, Tom Lane wrote:
> Dave Page writes:
> > For about a week, the Windows builds I've been running in Github have
> been
> > failing for PG17:
>
> Should be fixed as of a35801915 ?
>
Ah, yes - it does appear to be fine with head. I gu
me().string()');
=
It seems likely this is related to the DST change in the US, as the issue
started occurring on 4th November.
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
Hi
On Wed, 6 Nov 2024 at 16:11, Peter Eisentraut wrote:
> On 06.11.24 13:57, Ryohei Takahashi (Fujitsu) wrote:
> > The dll install paths are changed as follows on Windows.
> >
> > (1) pgevent.dll
> > PG16: lib/
> > PG17: bin/
> >
> > (2) dll for user (like libpq.dll, libecpg.dll)
> > PG16: Both
te file).
For those that don't know, the roaming profile directory on Windows is a
directory where a user's config/data files get synchronised onto each
machine they log into within the domain. The equivalent on Linux/macOS is a
file in ~/.pgadmin4/ or something along those lines. It is ab
nux, and have never seen it even
crash a whole machine, let alone render one unbootable. We also probably
have hundreds of thousands of users on Windows (based on the number of
downloads we get), and have never had such a problem reported.
--
Dave Page
pgAdmin: https://www.pgadmin.or
>
I kid you not, 20 seconds ago I hit send on a message on a pgAdmin thread
where I was complaining this bug was outstanding to someone asking about
GSSAPI support on Windows. That's quite the coincidence.
Anyway, no fix was committed as far as I know. I would suggest it shou
On Fri, 24 Jan 2025 at 20:07, Andrew Dunstan wrote:
>
> On 2025-01-22 We 4:25 AM, Dave Page wrote:
>
>
>
> On Wed, 22 Jan 2025 at 09:17, Daniel Gustafsson wrote:
>
>> > On 10 Jul 2024, at 19:06, Imran Zaheer wrote:
>>
>> (Reviving an old thread
On Sun, 6 Apr 2025 at 23:51, Daniel Gustafsson wrote:
> On 6 Mar 2025, at 14:12, Dave Page wrote:
> On Thu, 6 Mar 2025 at 12:19, Daniel Gustafsson wrote:
>
>> > On 6 Mar 2025, at 12:05, Dave Page wrote:
>> >
>> > Further to my previous patch to up
athan Katz, I just turned it into a patch.
This should be backpatched to all supported branches.
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
project_name_clarification_v1.diff
Description: Binary data
On Thu, 6 Mar 2025 at 12:19, Daniel Gustafsson wrote:
> > On 6 Mar 2025, at 12:05, Dave Page wrote:
> >
> > Further to my previous patch to update the licence preamble (
> https://www.postgresql.org/message-id/CA%2BOCxoy1Z05qDb1BfZZaVzT%3D6BrEW6u3wxprBkc7pewThJMoCA%40m
Per some brief discussion on the core list, the attached patch updates the
licence preamble to more accurately reflect the use of Postgres vs.
PostgreSQL (see https://www.postgresql.org/about/policies/project-name/ for
background from many years ago).
--
Dave Page
pgAdmin: https
; > CF entry should be marked closed no?
>
> Yep, just wanted to allow some time to see how the buildfarm liked it
> before
> closing. Done now, thanks for the reminder.
>
Thank you for dealing with this!
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
in pgweb commit
> 2d764dbc08.
>
Thanks Daniel - the patch looks good to me.
You'll push this to all active branches, correct?
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
e in there.
>
Great, thank you very much.
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
st be something different in your environment.
I do remember spending some time trying to resolve the "iconv failure: No
error" message myself though, but unfortunately I was just messing around
in the GitHub editor trying to get it to work for giggles at the time with
a bun
101 - 163 of 163 matches
Mail list logo
