I think the correct answer will be "all of them" :D maybe besides DOSBOX,
etc. because there are no DOS packages.
Also, I do not think you should send "Confidential" emails to public
mailing lists :)
Cheers,
Mateusz
pon., 21 paź 2024 o 13:33 Sunil Kumar napisał(a):
> Classification: *Confident
When you are performing PITR you need to configure a timestamp before your
last committed transaction. In your case you provided timestamp after your
last commit.
When postgtes is restoring until a specified point, it restores a
transaction from WAL, and checking if next transaction is before or a
Hey,
Check your parameter primary_conninfo on any standby server, you should
find here information about the user used for replication and its password
or path to .pgpass file, where the password is stored. If there is no
password or .pgpass file defined, then you do not need any password most
like
planation that hot standby archive wal files or not but I couldn't.
> Is this information from the Documentation?
>
> Best Regards,
> Alpaslan
>
> On Thu, Feb 8, 2024 at 9:24 PM Mateusz Henicz
> wrote:
>
>>
>> czw., 8 lut 2024 o 21:10 Laurenz Albe
>> nap
czw., 8 lut 2024 o 21:10 Laurenz Albe napisał(a):
> On Thu, 2024-02-08 at 09:23 +0100, Alpaslan AKDAĞ wrote:
> > Thank you for your answer.
> >
> > I have checked the pg_is_in_recovery() and here are the results
> > from primary and hot stand by server.
> >
> > Primary (old standby ):
> > select
Did you reconnect your replica after enabling log_hostname? If not, then do
it and check again.
śr., 1 lis 2023, 19:03 użytkownik Atul Kumar
napisał:
> I have already enabled log_hostname, still *client_hostname is not
> showing up.*
>
> Do you think that just because I use ip instead of hostna
Hey,
You are using "WITH tablespace_option" wrong.
Try it like this:
postgres=# CREATE TABLESPACE jme_tablespace OWNER jamiil LOCATION
'/database' WITH
(seq_page_cost=1.0,random_page_cost=4.0,effective_io_concurrency=1);
CREATE TABLESPACE
Cheers,
Mateusz
śr., 16 sie 2023 o 12:10 Amn Ojee Uw na
You can also just write an sql and execute it, like:
select 'alter user '|| usename ||' with password ''newpassword'';' from
pg_user;
\gexec
Cheers,
Mateusz
śr., 12 lip 2023 o 21:35 Gianni Ceccarelli
napisał(a):
> On 2023-07-12 Johnathan Tiamoh wrote:
> > I wish to find out if there is a way
Hi,
There should be another line in the log for why the logical replication
worker has stopped in the first place. Something like Primary Key or Unique
Constraint violation, timeout on WAL sender or receiver process, etc.
Unless you can provide that information I doubt someone will be able to
help
Hey,
If you would look into docs
https://www.postgresql.org/docs/current/app-pgrewind.html on the "Notes"
section you will find a list of permissions that user needs to have to be
able to run pg_rewind.
Cheers,
Mateusz
śr., 1 lut 2023, 15:09 użytkownik Wiwwo Staff napisał:
> Hi!
> Provided my r
Hi,
Adding a tag "nofailover: true" for nodes that can't be promoted to leaders
should do the trick.
https://patroni.readthedocs.io/en/latest/SETTINGS.html#tags
tags:
nofailover: true
Cheers,
Mateusz
pt., 9 gru 2022 o 11:03 Marco Lechner napisał(a):
> Hi,
>
>
>
> anyone who can point me
Hey,
There is pg_monitor role. I can "Read/execute various monitoring views and
functions. This role is a member of pg_read_all_settings, pg_read_all_stats
and pg_stat_scan_tables."
https://www.postgresql.org/docs/14/predefined-roles.html
Cheers,
Mateusz
wt., 6 gru 2022 o 13:37 Wiwwo Staff napi
Hey,
It is not a bug.
If you are using patroni, you should change your parameters in patroni
configuration yaml file, so the changes are reflected in your Distributed
Configuration Store. If you would look at the Patroni documentation (
https://patroni.readthedocs.io/en/latest/SETTINGS.html) you ca
Hi,
Did you check "SET SESSION AUTHORIZATION" or "SET ROLE" commands?
I think that is what you are looking for.
Cheers,
Mateusz
czw., 28 lip 2022 o 11:29 Wiwwo Staff napisał(a):
> Sorry to post solutions and links about alternative DBMSs, but I miss this
> sort of "sudo" ad database user level:
Hi,
Your first sentence is wrong. Changing pg_hba.conf file does not require
server restart. It is enough to reload the configuration using "pg_ctl
reload", "select pg_reload_conf();" in psql or just sending SIGHUP from
linux terminal to postmaster process after changing the pg_hba file.
To achiev
t; Thanks,
>
> Prabhakar
>
>
>
>
>
> Internal Use - Confidential
>
> *From:* Mahendrakar, Prabhakar - Dell Team
> *Sent:* Monday, June 20, 2022 4:22 PM
> *To:* Mateusz Henicz
> *Cc:* pgsql-general@lists.postgresql.org
> *Subject:* RE: Postgresql error : PANIC: c
ndr...@dellteam.com> napisał(a):
> Yes, We are using the pg_upgrade utility of Postgres.
>
>
>
> *From:* Mateusz Henicz
> *Sent:* Friday, June 17, 2022 3:31 PM
> *To:* Mahendrakar, Prabhakar - Dell Team
> *Cc:* pgsql-general@lists.postgresql.org
> *Subject:* Re: Postgresql error
Hi,
Have you done pg_upgrade post Postgres 13 installation?
https://www.postgresql.org/docs/13/pgupgrade.html
Cheers,
Mateusz
pt., 17 cze 2022 o 11:20 Mahendrakar, Prabhakar - Dell Team <
prabhakar.mahendr...@dellteam.com> napisał(a):
> Hello,
>
>
>
> Good Morning !
>
>
>
> We are facing *check
Do you have "recovery_target_timeline=latest" configured in your
recovery.conf or postgresql.conf? Depending on the version you are using,
up to 11 recovery.conf and postgresql.conf 12+.
Cheers,
Mateusz
wt., 15 cze 2021, 22:05 użytkownik email2ssk...@gmail.com <
email2ssk...@gmail.com> napisał:
19 matches
Mail list logo
