> ANY_VALUE aggregate: Yes: Yes: No: No: No: No: No: No: No: No: No: No: No:
> No: No: No: No: No: No ...
> www.postgresql.org
>
>
> pg_comebinebackup instead of pg_combinebackup
Fixed, thanks for the report!
--
Daniel Gustafsson
research which versions of which operating systems qualify.
From memory it's supported on FreeBSD, NetBSD and Linux with Windows, macOS and
OpenBSD not supporting it. Assuming I'm not completely wrong (a 1 minute
search shows it's in the ballpark) we could perhaps add something like
"Unsupported platforms include (but isn't limited to) Windows and macOS" which
would provide a bit more clarity.
--
Daniel Gustafsson
unts surely isn't one of those. And a quick grep
> through the code finds nothing applying PGC_S_OVERRIDE to it.
>
> What extensions do you have installed?
Also, is this by any chance a managed instance like Amazon RDS or Azure, or is
it a local database under your control?
--
Daniel Gustafsson
see if that works.
--
Daniel Gustafsson
mption
from queries being slow or did you capture plans for the queries which be
compared against "normal" production plans?
--
Daniel Gustafsson
ost appropriate (especially since md5
passwords are likely going away soon).
--
Daniel Gustafsson
stgreSQL to 16.3 without upgrading the
> .NET Framework?
Try PostgreSQL 16.4 instead, there was a known regression for very old Npgsql
versions in 16.3.
--
Daniel Gustafsson
ot affiliated with Libera Chat in any way and have no
control over their access policies. If you want to get in touch with other
postgres users there are numerous ways: this very mailing-list, Slack, Stack
Overflow etc.
--
Daniel Gustafsson
suggest you provide a lot more details. Which
installer was used? Where was it downloaded from? Which macOS version? Which
PostgreSQL version? Does the system log say anything? Is there enough space
on the partition? Do you have admin rights or is it a managed device? And so
on..
--
Daniel Gustafsson
equire manual
editing of the dump file to remove syntax not understood by the older
server."
Running the appropriate version of pg_dump for the target cluster, or applying
manual (or scripted) editing of the dump file is the option.
--
Daniel Gustafsson
; with "0" argument(s): "Authentication method not
> supported (Received: 10)"
Thats unfortunately a known regression in the latest minor releases, and will
be fixed in the upcoming releases. Using a recent version of npgsql and
ideally TLS1.3 is a workaround.
--
Daniel Gustafsson
stgresql.org/message-id/20190330192543.GH4719%40development
Hardware advances in the last five years may very well have made these findings
irrelevant however.
--
Daniel Gustafsson
> On 18 Jun 2024, at 19:28, Wiwwo Staff wrote:
> being able to tell psql to exclude some patterns from being stored in the
> .psql_history file
Off the cuff that sounds like a pretty useful thing to have.
--
Daniel Gustafsson
9805820567.pgcf%40coridan.postgresql.org#e151c884786c5ddf5bf49253964f841e
--
Daniel Gustafsson
.1, but
AF_UNIX is supported in 3+ IIRC. That being said, I agree with your (1).
--
Daniel Gustafsson
> On 22 May 2024, at 18:53, Tom Lane wrote:
>
> Daniel Gustafsson writes:
>> They are known to be zero, but that's not entirely equivalent though is it?
>> NIL is defined as ((List *) NULL) and NULL is typically defined as ((void *)
>> 0), so sizeof(0) would
e I know without looking up the
definition that some of the members are list. I like that readability. That
being said, I for sure won't fight if there is concensus to remove.
--
Daniel Gustafsson
; since the memset has written zeroes to the object "dpns", and these members
> are known to be zero.
They are known to be zero, but that's not entirely equivalent though is it?
NIL is defined as ((List *) NULL) and NULL is typically defined as ((void *)
0), so sizeof(0) would
loop for it to be measurable even?
--
Daniel Gustafsson
es/download/linux/debian.html. If you
propose a patch for the instructions, ideally on the pgsql-www@ mailinglist,
I'm sure we can ask Christophe (in CC:) for a review.
--
Daniel Gustafsson
t only for the schema, not the data.
--
Daniel Gustafsson
eing said, those
working on the Korean translations of strings are likely to be a good set of
people to start discussing with as they may have thought about it as well.
--
Daniel Gustafsson
> On 25 Mar 2024, at 15:09, Tom Lane wrote:
> My initial reaction is that we should warn only when the command
> is a complete no-op, that is none of the mentioned privileges
> matched.
That's my gut reaction too,
--
Daniel Gustafsson
ous grant to
> `lowpriv`, nothing actually changes in the ACL. This bit a client recently.
That's indeed a potential foot-gun.
> Is it worth generating a warning in this case?
Or maybe a NOTICE?
--
Daniel Gustafsson
> On 21 Mar 2024, at 14:27, Alvaro Herrera wrote:
>
> On 2024-Mar-21, Daniel Gustafsson wrote:
>
>> On 21 Mar 2024, at 13:28, Alvaro Herrera wrote:
>>
>>> I very much doubt that they realized that comments were going to be
>>> omitted. But cle
> On 21 Mar 2024, at 13:28, Alvaro Herrera wrote:
>
> On 2024-Mar-21, Daniel Gustafsson wrote:
>
>> Comments on roles are stored against the pg_authid catalog relation which is
>> the catalog used for dumping roles, but when using --no-role-passwords we
>> instea
. It kind of feels
like an accidental bug since the restored role will be in pg_authid where the
comment should be attached.
--
Daniel Gustafsson
are
very different things.
--
Daniel Gustafsson
I want show what changes ocurred on both versions, the page your are
> seeing and other you selected. But both on same page, not side by side.
Patches welcome, pgsql-www is the list for submitting changes for the website
and HTML rendering of the docs.
--
Daniel Gustafsson
ducing max_connections, is a good place
to start.
--
Daniel Gustafsson
ested in things found in
tables which makes it even easier.
--
Daniel Gustafsson
ou should be reading the version of
the docs which corresponds to the version you are running. If you are trying
to figure out an upgrade then the release notes are probably a better starting
point.
--
Daniel Gustafsson
egress.c;h=c894005dac06bc233896520c83c18e51af8ace9c;hb=HEAD#l1450
--
Daniel Gustafsson
l file in your source code repository then you should
use that. In essence, create the test database identically to how you create
the production database to ensure that you are testing what you will run in
production.
--
Daniel Gustafsson
o hence they aren't listed. Anyone still
running 10 or 11 is encouraged to upgrade to a supported version.
--
Daniel Gustafsson
ne that
can connect to the PostgreSQL database server to login as any
PostgreSQL user they wish, without the need for a password or any other
authentication."
I would recommend immediately reverting back to the scram-sha-256 setting and
figuring out why you were unable to login.
--
Daniel Gustafsson
> continue to receive the same error, any further suggestions ?
the _bf functions relate to the Blowfish cipher which was obsoleted in OpenSSL
3 so you need to load the legacy provider in your openssl configuration in
order to use it.
--
Daniel Gustafsson
d against.
--
Daniel Gustafsson
ificates in
> Wireshark, you need the TLS pre-master keys to decrypt the Encrypted
> Extensions packets.
There is no such thing, adding it yourself and debug your application using a
custom build is probably your best option.
--
Daniel Gustafsson
gresql usergroup or organization.
--
Daniel Gustafsson
> On 18 Jan 2024, at 00:59, Michael Nolan wrote:
> On Wed, Jan 17, 2024 at 5:32 PM Daniel Gustafsson wrote:
>>
>>> On 18 Jan 2024, at 00:24, Michael Nolan wrote:
>>> I reinstalled the devel package, still get the same unresolved symbol error.
>>
>>
da
>
> I reinstalled the devel package, still get the same unresolved symbol error.
My memory is failing me, but isn't CAST5 only available when loading the legacy
provider in OpenSSL 3? Which providers are loaded in your openssl config?
--
Daniel Gustafsson
eloper is free to
pursue whatever they choose. In that sense, postgres is very different from
products with clear owners like Oracle and MySQL.
--
Daniel Gustafsson
n the postgres project.
--
Daniel Gustafsson
> Or others (like PearsonVue)?
> Training and Certification path, source doc ?
>
> Regards
--
Daniel Gustafsson
h newer versions
of the server. You should use the dump/restore tools of the version you are
targeting. For other clients like psql it's usually fine to use the latest
version against older servers.
If you have a mix of server versions installed you need to put in the work of
ensuring you a
es. The
below threads may shine some light on the problem:
https://www.postgresql.org/message-id/flat/CABUevEx8KWhZE_XkZQpzEkZypZmBp3GbM9W90JLp%3D-7OJWBbcg%40mail.gmail.com
https://www.postgresql.org/message-id/flat/560A2239-5DE2-4B9C-92BC-878C6822F47C%40yesql.se#10b665b2193445a3d7f24be7917a9
y pgadmin developers. Reaching out to the relevant
pgadmin list is likely a better way to get answers:
https://www.pgadmin.org/support/list/
--
Daniel Gustafsson
TLS settings, etc)? If you apps and
other clients like psql can connect to the database it seems unlikely that a
pgAdmin wouldn't. It has a smell of trying to connect somewhere where nothing
is listening.
--
Daniel Gustafsson
esc ordering. Any query which relies on ordering, whichever is wanted,
should include an ORDER BY clause.
--
Daniel Gustafsson
> On 6 Sep 2023, at 21:23, Johnson, Bruce E - (bjohnson)
> wrote:
> What am I missing? (postgresql 15.4 running on Ubuntu 22.04), installed via
> postgresql.org apt repo.
The value should be within '', so listen_addresses = '10.128.206.109' should
work just fine.
--
Daniel Gustafsson
me the process is similar enough that it might be helpful
reading.
--
Daniel Gustafsson
> On 18 Jul 2023, at 12:26, Johnathan Tiamoh wrote:
>
> I used pg_ctl to stop the cluster.
>
> When I used the same pg_ctl to check status, it says no server is running
Right, but what does "pg_controldata" say for the cluster?
--
Daniel Gustafsson
ot; says "shut down". If you run the
same command, which state is the cluster reported to be in?
--
Daniel Gustafsson
inks: See the slack item)
>
> Can someone give me some advice?
The latter page website is actually hosted by a separate system and the change
in the menu content hasn't been synchronized there, hence why it's showing up.
We'll get it fixed, thanks for the report!
--
Daniel Gustafsson
> On 19 Jun 2023, at 21:00, Jeffrey Walton wrote:
> On Mon, Jun 19, 2023 at 11:39 AM Daniel Gustafsson wrote:
>>
>>> On 19 Jun 2023, at 17:13, Sebastien Flaesch
>>> wrote:
>>> OpenSSL V1 goes end of support soon (see
>>> https://www.openssl.
gt;
> On the various supported platforms?
PostgreSQL supports OpenSSL 3 and have done so for some time, each individual
packager and platform are however free to choose which OpenSSL version they
ship.
--
Daniel Gustafsson
ations. There has been patches proposed to add compression to libpq but
nothing has been added as of yet.
--
Daniel Gustafsson
L of such vintage is equally likely to be used in old
versions of postgres as current.
--
Daniel Gustafsson
pqinitopenssl_v2.diff
Description: Binary data
er things) in between these runs.
--
Daniel Gustafsson
ry to upgrade into this cluster, even just with the --check
option, does that yield more success?
--
Daniel Gustafsson
s at all, but uuid-ossp.dll is provided in the EDB packages
(looking at the binary zip bundle) so it's clearly available to be built.
Maybe someone from EDB can chime in with pointers for building on Windows so we
can update the docs accordingly?
--
Daniel Gustafsson
e way* you will for the upgrade and control
that.
--
Daniel Gustafsson
> On 15 Mar 2023, at 10:30, Dávid Suchan wrote:
> ..there are no other users in the db.
The check in question performs this:
SELECT COUNT(*) FROM pg_catalog.pg_roles WHERE rolname !~ '^pg_';
What do you get when running that in the new v14 cluster?
--
Daniel Gustafsson
a policy name (since none was explicitly violated).
--
Daniel Gustafsson
> Exactly. If our software is audited, how can I reliably prove to auditor
> that the running version of the procedure has not been tampered with
> either by customer, rogue developer or some malicious party?
How do you today prove that for other compiled programs in your system?
-
022-11-16-02:28:08 - org.postgresql.util.PSQLException: ERROR: unrecognized
> node type: 350
Are you running a version of JDBC which supports postgres 13?
--
Daniel Gustafsson https://vmware.com/
.postgresql.org/docs/release/15.0/
We should probably make those also show the same banner to avoid confusion like
this.
--
Daniel Gustafsson https://vmware.com/
> On 30 Sep 2022, at 17:36, Igor Korot wrote:
> Is building it myself the only option?
A quick googling indicates that there are options in the macOS package
managers:
https://formulae.brew.sh/formula/psqlodbc#default
--
Daniel Gustafsson https://vmware.com/
> On 12 Sep 2022, at 13:21, Peter Eisentraut
> wrote:
> On 11.09.22 23:43, Daniel Gustafsson wrote:
>>> On 11 Sep 2022, at 23:35, Tom Lane wrote:
>>> Should we document these functions as obsolete when using
>>> OpenSSL >= 1.1.0 ?
>> Given that 1
> On 11 Sep 2022, at 23:35, Tom Lane wrote:
>
> Daniel Gustafsson writes:
>> On 11 Sep 2022, at 17:08, Tom Lane wrote:
>>> Don't believe so. The HAVE_CRYPTO_LOCK stuff is all obsolete and
>>> not compiled if you built against 1.1.0. The only thing left
ppen if you don't call PQinitOpenSSL is an extra call to
> OPENSSL_init_ssl, which should be harmless as far as I can see
> from the OpenSSL docs.
To the best of my knowledge, thats entirely correct.
--
Daniel Gustafsson https://vmware.com/
;.
It will most likely be more helpful to ask Microsoft Azure in this case.
--
Daniel Gustafsson https://vmware.com/
y supposed to look for files that you need during the
> build.
So by that logic, do you think the AC_CHECK_FILE call should be removed?
--
Daniel Gustafsson https://vmware.com/
ould print something, it looks like this will do:
+1, looks reasonable.
> +elif test x"$cross_compiling" = x"yes"; then
I noticed that we test without the x"foo" = x"yes" construction for zic (line
1135), should we change that while at it and be consistent for all
$cross_compiling uses?
--
Daniel Gustafsson https://vmware.com/
)
-
- if test x"$ac_cv_file__dev_urandom" = x"no" ; then
-AC_MSG_ERROR([
-no source of strong random numbers was found
-PostgreSQL can use OpenSSL, native Windows API or /dev/urandom as a source of
random numbers.])
- fi
fi
--
Daniel Gustafsson https://vmware.com/
n/2287-anonymization-and-data-masking-with-postgresql/
--
Daniel Gustafsson https://vmware.com/
> On 14 Oct 2021, at 14:34, Cedric Rey wrote:
> the certificate on download.postgresql.org has expired :
Are you perhaps running an old version of OpenSSL?
--
Daniel Gustafsson https://vmware.com/
yle
tests, and personally I always install to a specific folder (see the section on
developer options):
./configure --enable-debug --enable-tap-tests --prefix=path/to/dev/install
Feel free to reach out here if you get stuck on anything, so we can make the
Wiki page better.
--
Daniel Gustafsson https://vmware.com/
s a point to knowing just which ones were
used. Connection level parameters should probably be scrubbed, but
object-level filtering etc could be handy.
Would you like to try and propose a patch for pg_dump to implement this?
--
Daniel Gustafsson https://vmware.com/
> On 26 Aug 2021, at 16:59, Peter Eisentraut
> wrote:
> On 26.08.21 10:40, Daniel Gustafsson wrote:
>> Wouldn’t the difference in possible error messages in upper/lower be able to
>> leak whether the input is ascii or wide chars, and/or the collation?
>
> Yeah,
be worth taking a careful look and possibly
> lifting this restriction.
Wouldn’t the difference in possible error messages in upper/lower be able to
leak whether the input is ascii or wide chars, and/or the collation?
--
Daniel Gustafsson https://vmware.com/
s well in case there are more
detailed questions.
--
Daniel Gustafsson https://vmware.com/
> On 30 Jan 2018, at 12:32, Findlay, Thomas C
> wrote:
>
> Hello,
>
> How do you load GIS shapefiles into a pgAdmin database, using pgAdmin 4?
>
> I have done this in pgAdmin 3 using the PostGIS Shapefile loader, but can’t
> seem to find this in version 4.
In case noone here knows the ans
> On 26 Nov 2017, at 17:54, chandra sekhar wrote:
>
> sql server has msdb database which stores the history of backups taken.
> is there any table in postgres which keep track of when the archive log files
> are archived ?
This is the mailinglist for the postgresql.org website, you are better o
85 matches
Mail list logo