Hello,
We're using pg_dumpall (from 14.1) to dump older clusters and
restore them into a new 14.1 cluster. The dump contains some databases
together with roles etc.
Is there some easy way to restore only one database out of this dump
file?
Thanks in advance
matthias
--
Matthias Apitz,
On Mon, Dec 20, 2021 at 03:22:31PM +0100, Christoph Moench-Tegeder wrote:
> Active FIPS mode (/proc/sys/crypto/fips_enabled => 1) on the server does
> produce this behaviour.
Most likely, this is a build linked with OpenSSL? The way MD5 hashes
are computed in Postgres has largely changed in 14, a
Matthias Apitz writes:
> We're using pg_dumpall (from 14.1) to dump older clusters and
> restore them into a new 14.1 cluster. The dump contains some databases
> together with roles etc.
> Is there some easy way to restore only one database out of this dump
> file?
No; pg_dumpall's output is jus
Is it possible to specify the publication name to be refreshed in case I do not
want to refresh all publications of the subscription?
Something like:
alter subscription subscription_name refresh publication publication_name
Thanks
IMPORTANT - This email and any attachments is intended for the abo
Michael Paquier writes:
> On Mon, Dec 20, 2021 at 03:22:31PM +0100, Christoph Moench-Tegeder wrote:
>> Active FIPS mode (/proc/sys/crypto/fips_enabled => 1) on the server does
>> produce this behaviour.
> Most likely, this is a build linked with OpenSSL? The way MD5 hashes
> are computed in Post
I don't use pacman for PostgreSQL.
I compile from source.
Seems as though this error shouldn't happen.
On Wed, Dec 22, 2021 at 5:24 PM Adrian Klaver
wrote:
> On 12/22/21 2:14 PM, Theodore M Rolle, Jr. wrote:
> Please reply to list also.
> Ccing list.
>
> From below, what did pacman -Syyuu do?
>
Στις 4/1/22 5:47 μ.μ., ο/η Avi Weinberg έγραψε:
Is it possible to specify the publication name to be refreshed in case
I do not want to refresh all publications of the subscription?
Something like:
alter subscription subscription_name refresh publication publication_name
Here is the method:
"Theodore M Rolle, Jr." writes:
> I don't use pacman for PostgreSQL.
> I compile from source.
The point is that your from-source build of psql might be linking
to an out-of-date copy of libpq.so provided by the OS. Linux
machines tend to do that (i.e., prefer libraries in /usr/lib[64])
unless yo
Hello,
I left process as described in previous message.
That's after people on irc confirmed that using libpq across versions is fine,
and realizing that libpq is just a client to talk to server, and doesn't
implement other server functionality.
W dniu 25.11.2021 o 21:17, Laurent FAILLIE pisze:
## Michael Paquier (mich...@paquier.xyz):
> On Mon, Dec 20, 2021 at 03:22:31PM +0100, Christoph Moench-Tegeder wrote:
> > Active FIPS mode (/proc/sys/crypto/fips_enabled => 1) on the server does
> > produce this behaviour.
>
> Most likely, this is a build linked with OpenSSL? The way MD5 hashes
ldd /usr/local/pgsql/bin/psql
linux-vdso.so.1 (0xa2bef000)
libpq.so.5 => /USR/local/lib/libpq.so.5 (0xa2aaf000)
libreadline.so.8 => /usr/lib/libreadline.so.8 (0xa2a1d000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0xa29ed000)
libm.so.6 => /usr/lib/libm.so.6 (0x
"Theodore M Rolle, Jr." writes:
> ldd /usr/local/pgsql/bin/psql
> linux-vdso.so.1 (0xa2bef000)
> libpq.so.5 => /USR/local/lib/libpq.so.5 (0xa2aaf000)
> libreadline.so.8 => /usr/lib/libreadline.so.8 (0xa2a1d000)
> libpthread.so.0 => /usr/lib/libpthread.so.0 (0xa29ed0
On 1/4/22 13:15, Chocimier wrote:
Hello,
I left process as described in previous message.
That's after people on irc confirmed that using libpq across versions is
fine,
and realizing that libpq is just a client to talk to server, and doesn't
implement other server functionality.
As long as
On Tue, Jan 04, 2022 at 12:54:35PM -0500, Tom Lane wrote:
> I reproduced this on Fedora 35 with FIPS mode enabled. The problem
> is that OpenSSL treats MD5 as a disallowed cipher type under FIPS
> mode, so this call in pg_cryptohash_init fails:
Is that 3.0.0 or 1.1.1? I can see the following, te
Michael Paquier writes:
> On Tue, Jan 04, 2022 at 12:54:35PM -0500, Tom Lane wrote:
>> I reproduced this on Fedora 35 with FIPS mode enabled. The problem
>> is that OpenSSL treats MD5 as a disallowed cipher type under FIPS
>> mode, so this call in pg_cryptohash_init fails:
> Is that 3.0.0 or 1.1
On Wed, Jan 05, 2022 at 01:08:53AM -0500, Tom Lane wrote:
> I think it's very important that the error message in this case
> mention "FIPS mode" explicitly. Otherwise, people will have no
> idea that that's where the problem originates, and they'll be
> frustrated and we'll get bug reports. (The
16 matches
Mail list logo
