.com |
>
>
> *Services provided by HCL on behalf of Google*
>
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
applicable
> to the PGAdmin 4 application? Thank you very much!!
>
There are no STIGs for pgAdmin.
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
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
; > 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
On Wed, 19 Mar 2025 at 12:42, Akshay Joshi
wrote:
>
>
> On Wed, Mar 19, 2025 at 5:11 PM Dave Page wrote:
>
>>
>>
>> On Wed, 19 Mar 2025 at 11:12, Akshay Joshi
>> wrote:
>>
>>> Hi Dave/Hackers,
>>>
>>> I have started work
pdates manually then can
> prefer this and if update is available then the *"Restart to update"*
> option will show and if clicked will quit the app and install the latest
> version.
>
> Let me know in which way we can proceed.
>
Option 1 seems good to me; though the curre
backend.
>
> Any other solution or suggestion?
>
This seems like it would be a very large amount of work, for very little
gain, and would certainly be inconsistent with how we would expect to
browse files and folders for example. I do not think it is worth the effort.
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
On Mon, 17 Mar 2025 at 10:11, Aditya Toshniwal <
aditya.toshni...@enterprisedb.com> wrote:
>
>
> On Mon, Mar 17, 2025 at 3:39 PM Dave Page wrote:
>
>> Hi
>>
>> On Mon, 17 Mar 2025 at 09:39, Aditya Toshniwal <
>> aditya.toshni...@enterprisedb.com&g
Hi
On Mon, 17 Mar 2025 at 09:39, Aditya Toshniwal <
aditya.toshni...@enterprisedb.com> wrote:
> Hi Dave,
>
> On Mon, Mar 17, 2025 at 3:00 PM Dave Page wrote:
>
>> Hi
>>
>> On Mon, 17 Mar 2025 at 09:11, Aditya Toshniwal <
>> aditya.tosh
cating
server functionality anyway.
> Tools
>
>1. Tool access like query tool, backup, etc.
>
> Storage Manager:
>
>1. Create/Edit/Delete file.
>2. Create/Edit/Delete folders.
>
>
> On Thu, Mar 13, 2025 at 8:47 PM Aditya Toshniwal <
> aditya.t
On Thu, 13 Mar 2025 at 13:19, Aditya Toshniwal <
aditya.toshni...@enterprisedb.com> wrote:
>
>
> On Thu, Mar 13, 2025 at 4:54 PM Dave Page wrote:
>
>>
>>
>> On Thu, 13 Mar 2025 at 11:07, Aditya Toshniwal <
>> aditya.toshni...@enterprisedb.com> wro
ters used in the JSON (excluding the
password that we can prompt for of course)?
>
> Thanks,
> Yogesh Mahajan
> EnterpriseDB
>
>
> On Thu, Mar 13, 2025 at 4:59 PM Dave Page wrote:
>
>> Hi
>>
>> On Thu, 13 Mar 2025 at 11:20, Yogesh Mahajan <
>> yogesh.m
Hi
On Thu, 13 Mar 2025 at 11:20, Yogesh Mahajan <
yogesh.maha...@enterprisedb.com> wrote:
> Hi Dave,
>
> Couple of follow up questions -
>
> Thanks,
> Yogesh Mahajan
> EnterpriseDB
>
>
> On Thu, Mar 13, 2025 at 4:37 PM Dave Page wrote:
>
>>
>&
On Thu, 13 Mar 2025 at 11:07, Aditya Toshniwal <
aditya.toshni...@enterprisedb.com> wrote:
> Hi Dave,
>
> On Thu, Mar 13, 2025 at 4:27 PM Dave Page wrote:
>
>>
>>
>> On Thu, 13 Mar 2025 at 10:26, Aditya Toshniwal <
>> aditya.toshni...@enterprisedb.co
ow may get additional in future.
>
Yes :-). Ideally, as much of the original state as possible should be
restored.
> 2.Can we use an existing crypt key to encrypt the query data or simply
> json encoding should be enough?
>
We're already storing the query history, so we should f
On Thu, 13 Mar 2025 at 10:26, Aditya Toshniwal <
aditya.toshni...@enterprisedb.com> wrote:
> Hi Dave,
>
> On Thu, Mar 13, 2025 at 3:36 PM Dave Page wrote:
>
>> Hi
>>
>> On Thu, 13 Mar 2025 at 06:16, Aditya Toshniwal <
>> aditya.toshni...@enterprisedb.
signed to users.
>7. Permissions will be used to
>8. Admin role remains static with no changes allowed.
>
> Let me know your thoughts on this. If everything looks good then I will
> proceed.
>
What permissions would we support initially?
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
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
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
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
sabled tabs. The tabs
> will enable/disable based on the format selected.
>
> Please share your feedback on this.
>
>
> [image: image.png]
>
Normally when something is disabled, it is simply greyed out and made to
not respond to input. Why not do the same here instead of de
On Thu, 20 Feb 2025 at 10:56, Aditya Toshniwal <
aditya.toshni...@enterprisedb.com> wrote:
> Hi Dave,
>
> On Thu, Feb 20, 2025 at 3:22 PM Dave Page wrote:
>
>>
>>
>> On Thu, 20 Feb 2025 at 03:52, Aditya Toshniwal <
>> aditya.toshni...@enterprisedb.co
On Thu, 20 Feb 2025 at 03:52, Aditya Toshniwal <
aditya.toshni...@enterprisedb.com> wrote:
> Hi Dave,
>
> On Wed, Feb 19, 2025 at 6:55 PM Dave Page wrote:
>
>>
>>
>> On Wed, 19 Feb 2025 at 12:24, Yogesh Mahajan <
>> yogesh.maha...@enterprisedb.com&
On Wed, 19 Feb 2025 at 12:24, Yogesh Mahajan <
yogesh.maha...@enterprisedb.com> wrote:
>
> Hi,
>
> On Wed, Feb 19, 2025 at 5:12 PM Dave Page wrote:
>
>> Hi
>>
>> On Thu, 16 Jan 2025 at 06:37, Aditya Toshniwal <
>> aditya.toshni...@enterprisedb.com&
t;> <https://twitter.com/edbpostgres?lang=en>
>>>> <https://www.facebook.com/EDBpostgres>
>>>> <https://www.instagram.com/EDBpostgres/>
>>>>
>>>>
>>>> On Mon, Aug 19, 2024 at 11:40 AM Aditya Toshniwal <
>&g
On Thu, 13 Feb 2025 at 11:25, Aditya Toshniwal <
aditya.toshni...@enterprisedb.com> wrote:
> Hi Dave,
>
> On Thu, Feb 13, 2025 at 4:30 PM Dave Page wrote:
>
>>
>>
>> On Thu, 13 Feb 2025 at 10:51, Aditya Toshniwal <
>> aditya.toshni...@enterprisedb.
It's not entirely what Dave is suggesting. He's suggesting the split
> button dropdown should have a checkmark to set the default behaviour of the
> button.
> @Dave Page In that case it will contradict with Save
> and Save As. Save As here is an extension of the menu and not th
t tab as it did before the change. If I have windows open, I am
>> already logged into a server, and I am not going to go through another
>> login... Especially since I probably have my credentials saved in the
>> 'Default Workspace' tab, so it's mu
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
lling multiple times. At this
>>> point, I cannot even run the software because of this issue.
>>>
>>>
>>>
>>> This is the most frustrating experience I have ever had with software
>>> installation by a fair margin, but I really need to learn SQL and would
>>> like to use this tool.
>>>
>>> Is there any way to completely uninstall it, and start again, and get
>>> the permissions resolved? I have spent days asking chatbots to resolve this
>>> issue but their help was insufficient. Again, psql works fine, but I want
>>> to be able to follow along with a course taught with the actual tool.
>>>
>>> Thanks,
>>>
>>> Brian
>>
>>
>>
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
>
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
SAPI
support would be trivial, if the upstream bug were fixed.
[1]
https://www.postgresql.org/message-id/flat/CA%2BOCxoxwsgi8QdzN8A0OPGuGfu_1vEW3ufVBnbwd3gfawVpsXw%40mail.gmail.com
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
rsor*.
>
That might be our solution in general - have a per-query-tool-instance
option to specify client or server cursor. If you choose server, you lose
the row count, but get the performance. If you choose client, you get the
current behaviour.
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
On Thu, 5 Dec 2024 at 12:51, Dave Caughey wrote:
> On Thu, 5 Dec 2024 at 04:18, Dave Page wrote:
>
>>
>> As of last month, I now work for pgEdge
>>
>
> Congratulations, Dave. I hope this chapter is fruitful!
>
Thank you!
--
Dave Page
pgAdmin: https://
for the initial version we simply disable auto-update
for machine wide installations, and think about supporting them for admin
users in the future when we can properly check that we have the desired
permissions. We should also consider changes to the installer - e.g.
perhaps make the per-user in
://www.pgadmin.org/download/
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.pgadmin.org_download_&d=DwMDaQ&c=bFSfV3JDZVFjkVdrOg1Bnsgwku-x_EGNRi2KNxwvClI&r=BVimxxP14A5Y9v1FyBC4bZqSXEI8yYvsHR8N3ntPynE&m=5URAXPH0pwJYyURsLPVCQ8CMSMXJnAEXfWUrSHZ3Fqbp7zaaoRs4BZu18MhMQ5_N&s=nJDxhu5Tb_r_IXFCodxCgow_-KBhj_PjY6sQNbmfq_A&e=>
>
>
> Ray.
>
>
>
>
> --
>
> Raymond O'Donnell // Galway // Ireland
>
> r...@rodonnell.ie
>
>
>
> --
> Raymond O'Donnell // Galway // ireland...@rodonnell.ie
>
>
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
s, as we are using Inno setup for creating our Windows
> installer, we can try updating our application with existing way only, if
> something does not work then we have the option to change our installer
> creation process.
>
So one thing that springs to mind is that on Windows, thi
t; when adding shared servers. In future, it can be helpful as a filter
> criteria. If you agree then I can create a git issue. Below is a sample.
> Let me know what you think.
>
> [image: Screenshot 2024-11-28 at 15.44.28.png]
>
That seems like it could be useful.
--
Dave Page
pgAdmin
m one of them *must* be used? Our current
installer is pretty standard in the way it works, so I'm curious to know if
we would actually need to change technology for a specific reason.
Thanks!
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
- Added appropriate icons for the "Disconnect" and "Delete"
>>> actions.
>>>
>>> I would like your input on whether these changes should be applied
>>> universally across all delete and disconnect scenarios, or if they should
>>> be limited to just the database delete and disconnect actions.
>>>
>>> Please find the attached screenshots showcasing the changes.
>>>
>>>
>>> Thank you for your feedback!
>>>
>>> Best regards,
>>> Rohit Bhati
>>>
>>>
>>>
>>
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
e it.
>
Or do some string substitution in the command, e.g.
/path/to/passexec.sh $HOST$ $PORT$
or similar, so the user has even more flexibility. I know that is done in
PEM in a few places, possibly in pgAdmin too, though I don't recall offhand
(if it is, we should be consistent on how the param
vironment variables.
>
>
> Please share your suggestions or feedback on the approach I am proposing.
>
I'm not sure why the user would need to set environment variables -
wouldn't pgAdmin just set them in the environment of the passexec
process, based on the server definitio
d resources for supporting and testing on
different architectures and platforms.
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
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
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
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
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
gt;>>>3. Mui 5
>>>>>4. Code Mirror 6
>>>>>5. React Aspen tree with React Arborist (
>>>>>https://www.npmjs.com/package/react-arborist)
>>>>>
>>>>>
>>>>> --
>>>>> Akshay Joshi
>>>>> Principal Software Architect
>>>>> www.enterprisedb.com
>>>>>
>>>>> *Blog*: https://www.enterprisedb.com/akshay-joshi
>>>>> *GitHub*: https://github.com/akshay-joshi
>>>>> *LinkedIn*: https://www.linkedin.com/in/akshay-joshi-086497216
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> <http://www.enterprisedb.com>
>>>>
>>>> Pravesh Sharma
>>>>
>>>> Software Engineer
>>>>
>>>> +91 9406461406
>>>>
>>>> www.enterprisedb.com
>>>>
>>>> Power to Postgres
>>>>
>>>> <https://www.linkedin.com/company/edbpostgres>
>>>> <https://twitter.com/edbpostgres?lang=en>
>>>> <https://www.facebook.com/EDBpostgres>
>>>> <https://www.instagram.com/EDBpostgres/>
>>>>
>>>
>
> --
>
>
> Pravesh Sharma
>
> Senior SDE
>
> +91 9406461406
>
>
> enterprisedb.com
>
--
Dave Page
VP, Chief Architect, Database Infrastructure
EDB: https://www.enterprisedb.com
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 Tue, 8 Oct 2024 at 16:30, Pravesh Sharma
wrote:
> Hi Dave,
>
> On Tue, Oct 8, 2024 at 6:34 PM Dave Page wrote:
>
>>
>>
>> On Tue, 8 Oct 2024 at 13:56, Pravesh Sharma <
>> pravesh.sha...@enterprisedb.com> wrote:
>>
>>> Hi Hacker
ype is character.
>
> Please provide your suggestions which solution looks good to you.
>
Why not include the length in the cast? We know what the input string is,
so can't we just do the equivalent of:
'pgadmin'::character(7);
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
EDB: https://www.enterprisedb.com
; On Tue, Sep 10, 2024 at 2:42 PM Dave Page wrote:
>
>> Hi
>>
>> Shadow is more visible, but it doesn't really follow the material UI
>> styling which is flat rather than 3D.
>>
>> I think Anil's idea is worth exploring; remove the alternatin
ards
> Rohit Bhati
>
>
> On Mon, Sep 9, 2024 at 4:11 PM Rohit Bhati
> wrote:
>
>> I already set weight to 900.
>> If we need to be more distinct then I think we can have some shadow or if
>> anything else please suggest.
>>
>> On Mon, Sep 9, 2024 at
till needs
more weight.
>
> Thanks
> Rohit Bhati
> EnterpriseDB
>
>
> On Fri, Sep 6, 2024 at 2:01 PM Dave Page wrote:
>
>>
>>
>> On Fri, 6 Sept 2024 at 09:25, Rohit Bhati
>> wrote:
>>
>>> I have made some more changes with cha
.
>
> On Fri, Sep 6, 2024 at 1:51 PM Dave Page wrote:
>
>> Hi
>>
>> On Fri, 6 Sept 2024 at 09:19, Rohit Bhati
>> wrote:
>>
>>> Hi,
>>>
>>> I have removed the border and background color, just made the row
>>> numbe
e - and I think we still need some other
visual distinction, such as the column background colour.
>
>
> On Fri, Sep 6, 2024 at 12:35 PM Khushboo Vashi <
> khushboo.va...@enterprisedb.com> wrote:
>
>>
>>
>> On Thu, Sep 5, 2024 at 7:11 PM Dave Page wrote:
&g
ght not be to
me, but I haven't tested.
I wonder also if we should make the row numbers bold all the time. Thoughts?
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
EDB: https://www.enterprisedb.com
PGDay UK 2024, 11th September, London: https://2024.pgday.uk/
7;s the one :-)
>
>
> Rohit Bhati
> EnterpriseDB
>
> On Thu, Sep 5, 2024 at 3:51 PM Dave Page wrote:
>
>> Hi
>>
>> On Thu, 5 Sept 2024 at 08:27, Rohit Bhati
>> wrote:
>>
>>> Hi Hackers,
>>>
>>> Please check the up
distinction from the data columns. Probably worth
working on that one at the same time?
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
EDB: https://www.enterprisedb.com
PGDay UK 2024, 11th September, London: https://2024.pgday.uk/
On Tue, 3 Sept 2024 at 10:51, Yogesh Mahajan <
yogesh.maha...@enterprisedb.com> wrote:
>
> Thanks,
> Yogesh Mahajan
> EnterpriseDB
>
>
>
> On Tue, Sep 3, 2024 at 3:11 PM Dave Page wrote:
>
> Hi
>
> Hi
>>
>> On Tue, 3 Sept 2024 at 10:32, Yoge
only load the servers once into any
given configuration database.
>
> Also, on restart admin user specified while container is not recreated.
> Can't we fix on similar lines?
>
> Thanks,
> Yogesh Mahajan
> EnterpriseDB
>
>
> On Tue, Sep 3, 2024 at 2:05 PM Dave Page wr
On Tue, 3 Sept 2024 at 09:29, Pravesh Sharma <
pravesh.sha...@enterprisedb.com> wrote:
> Hi Dave,
>
> On Tue, Sep 3, 2024 at 1:47 PM Dave Page wrote:
>
>> Hi
>>
>> On Tue, 3 Sept 2024 at 09:10, Pravesh Sharma <
>> pravesh.sha...@enterprisedb.com> w
ts in the database. If it does, we would skip
> registering it again.
>
>
> Please share any suggestions or feedback on this approach.
>
I would say "Won't fix". If someone is using persistent storage for
settings, why launch containers to import the same servers over a
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
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.
--
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
ated to panels in the pgAdmin 4's configured database file. Through
> debouncing we will be able to call the API at certain intervals of user
> interaction, and it will update the stored data related to workspace and
> all other panels.
>
OK.
--
Dave Page
pgAdmin: https://www.pg
On Thu, 8 Aug 2024 at 13:46, Yogesh Mahajan
wrote:
> Hi Dave,
>
> Should I proceed with this approach?
>
Sure, go ahead.
>
> Thanks,
> Yogesh Mahajan
> EnterpriseDB
>
>
> On Thu, Aug 8, 2024 at 6:14 PM Dave Page wrote:
>
>>
>>
>> On Thu
On Thu, 8 Aug 2024 at 13:38, Yogesh Mahajan
wrote:
>
>
> Hi,
>
> On Thu, Aug 8, 2024 at 5:58 PM Dave Page wrote:
>
>>
>>
>> On Mon, 5 Aug 2024 at 13:27, Yogesh Mahajan <
>> yogesh.maha...@enterprisedb.com> wrote:
>>
>>> Hi Hacker
.
>
That sounds almost like returning to the way things used to work with the
master password, except we auto-generate it, and store that in the
keychain. I assume we'd do the same on all platforms, using whatever the
equivalent store is on each?
Any idea why it asks for the login passwo
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'
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 Wed, 24 Jul 2024 at 13:55, Aditya Toshniwal <
aditya.toshni...@enterprisedb.com> wrote:
> Hi Dave,
>
>
>
> On Wed, Jul 24, 2024 at 6:15 PM Dave Page wrote:
>
>>
>>
>> On Wed, 24 Jul 2024 at 13:37, Aditya Toshniwal <
>> aditya.toshni...@
>>>>>>>> Yogesh, could you please verify this for Thursday's release?
>>>>>>>>
>>>>>>>> *Note:- We have transitioned from NW.js to Electron starting with
>>>>>>>> this release.*
>>>>>>>>
>>>>>>>>
>>>>>>>> Akshay Joshi
>>>>>>>>
>>>>>>>> Principle Software Architect
>>>>>>>>
>>>>>>>> enterprisedb.com
>>>>>>>>
>>>>>>>> * Blog*: https://www.enterprisedb.com/akshay-joshi
>>>>>>>> * GitHub*: https://github.com/akshay-joshi
>>>>>>>> * LinkedIn*: https://www.linkedin.com/in/akshay-joshi-086497216
>>>>>>>>
>>>>>>>
>>>>>
>>>>> --
>>>>> Thanks,
>>>>> Aditya Toshniwal
>>>>> pgAdmin Hacker | Sr. Software Architect | *enterprisedb.com*
>>>>> <https://www.enterprisedb.com/>
>>>>> "Don't Complain about Heat, Plant a TREE"
>>>>>
>>>>
>>>
>>> --
>>> Thanks,
>>> Aditya Toshniwal
>>> pgAdmin Hacker | Sr. Software Architect | *enterprisedb.com*
>>> <https://www.enterprisedb.com/>
>>> "Don't Complain about Heat, Plant a TREE"
>>>
>>
>
> --
> Thanks,
> Aditya Toshniwal
> pgAdmin Hacker | Sr. Software Architect | *enterprisedb.com*
> <https://www.enterprisedb.com/>
> "Don't Complain about Heat, Plant a TREE"
>
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
EDB: https://www.enterprisedb.com
PGDay UK 2024, 11th September, London: https://2024.pgday.uk/
cales/getlocales.cpp
> and then substitute some patterns (
> https://github.com/EnterpriseDB/edb-installers/blob/REL-16/server/pgserver.xml.in#L2850)
> I'm not sure why we do that but that is the old code and probably @Dave
> Page may know but I'm not sure if that piece of code is
pect that Windows accepts the POSIX style en_US too, but
>>> it's not what the manual tells you to use.
>>>
>>> But really we shouldn't have to know or care how locales are named; we
>>> should get the names from the OS in the first place, and then we
>>> should remember them and give them back to the OS at the right times.
>>> The two problems here is that Windows has two kinds, one unstable over
>>> time and with illegal (for us) characters in the name, and one stable;
>>> we need to find all the places where the old unstable ones can get
>>> into our system, and block them off. I'm aware of two places now: the
>>> EDB installer, and initdb's default for people who run it on the
>>> command line with giving an explicit name.
>>>
>>> > I can help with the testing part. Let me know the details, please.
>>>
>>> Thanks! I will rebase that patch, and CC you on the thread.
>>>
>>> [1]
>>> https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html
>>>
>>
>>
>> --
>> Sandeep Thakkar
>>
>>
>>
>
> --
> Sandeep Thakkar
>
>
>
--
Dave Page
VP, Chief Architect, Database Infrastructure
EDB: https://www.enterprisedb.com
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
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 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
> > >
> > >
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: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
>
/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
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
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
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
&
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,
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!
>
>
>
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
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
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
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
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
definite benefits, but there is the downside of having to
scroll and click to browse results. Personally I'm fine with that, but I
think you should probably poll pgadmin-support for opinions from more users.
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
EDB: https://www.enterprisedb.com
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
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
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
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
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
1 - 100 of 9301 matches
Mail list logo
