Re: ora2pg -c ora2pg.conf -t COPY -a tablename not working properly

On Fri, Aug 25, 2023 at 5:49 PM duc hiep ha wrote: > > Hi, > > I've just found the root cause! In this command: > ora2pg -c ora2pg.conf -t COPY -a tablename > I have created and changed the name of table in postgres. It will not work > like that if i don't put replace_table option in config file.

PL/Perl function signatures

Hi all, is there any way to exploit sub signatures in PL/Perl? The following is not working, I suspect it is not possible due to the way PL/Perl compiles the code. testdb=# create or replace function f( a int ) returns text as $$ use feature 'signatures'; elog( INFO, "Perl version $^V" ); elog(I

Re: Role for just read the data + avoid CREATE / ALTER / DROP

Dear Thomas, Dear All! Thank you for the answers, and explanations! Thomas Kellerer ezt írta (időpont: 2023. aug. 25., P, 16:02): > > With Postgres 15 it should be as simple as: > >CREATE ROLE CREATE ROLE u_tdb_ro WITH LOGIN; >GRANT pg_read_all_data TO u_tdb_ro; > > In previous versions

Re: ora2pg -c ora2pg.conf -t COPY -a tablename not working properly

Yes, you are right. Thank you Brs Hans Vào Th 2, 28 thg 8, 2023 lúc 14:43 Luca Ferrari đã viết: > On Fri, Aug 25, 2023 at 5:49 PM duc hiep ha > wrote: > > > > Hi, > > > > I've just found the root cause! In this command: > > ora2pg -c ora2pg.conf -t COPY -a tablename > > I have created and change

Re: Support for Deferred Constraints in PG15 Logical Replication

On Fri, 2023-08-25 at 00:28 +0200, Jitesh Srivastava wrote: > I'm interested in finding out whether logical replication in PostgreSQL 15 > includes support for deferrable unique constraints. You can have deferrable constraints on both ends, yes. If you wonder whether SET CONSTRAINTS ALL DEFERRE

PostgreSQL 12 reindex

How to safely perform a reindex partitioned tables (postgresql 12) Regards, Jk

Re: PostgreSQL 12 reindex

It’s good idea do that like this: REINDEX TABLE CONCURRENTLY partitioned_table_1 REINDEX TABLE CONCURRENTLY partitioned_tab_2 REINDEX TABLE CONCURRENTLY partitioned_table_3 Regards, JK > Wiadomość napisana przez Joseph Kennedy w dniu > 28.08.2023, o godz. 15:51: > > How to safely perform

回复: ident auth does not works as usual

Hi "Show your psql command that is failing." [root@~ pg]# /usr/local/pgsql/bin/psql -p5432 -d db1 -h127.0.0.1 psql: error: connection to server at "127.0.0.1", port 5432 failed: FATAL: Ident authentication failed for user "root" If the error is Ident authentication failed for user "cce"

回复: ident auth does not works as usual

Hi, Sorry, the name of ident file that i used is wrong, it is pg_ident.conf (the same as you says） And, I found pg_ident.conf works, because i can found ident entry in pg views , line_number | map_name | sys_name | pg_username | error -+--+--+-+-

Re: ident auth does not works as usual

On Mon, Aug 28, 2023 at 7:34 AM pan snowave wrote: > But when i connect to psserver by using os user root > /usr/local/pgsql/bin/psql -p5432 -d db1 -h127.0.0.1 > If you want to login as the cce role add " -U cce " to your command line (or one of the various other ways you can specify a db

pg_visible_in_snapshot clarification

Hey There, I'm looking for some clarification around pg_visible_in_snapshot function. As it seems to not be working the way I would expect or the way the documentation is setup. I've attempted this on pg13 and pg15 and am getting the same behaviour. 3 connections via psql 2 to the primary and

auto vacuum question

All, We recently changed the name of the superuser role in our database, and then noticed some issues with the autovacuum processes.  We are running 15.3, and had a login role, lets call it 'red', which had the superuser attribute assigned to it.   This was the original owner/creator of all the da

Re: auto vacuum question

On 8/28/23 13:06, Alan Stange wrote: All, We recently changed the name of the superuser role in our database, and then noticed some issues with the autovacuum processes.  We are running 15.3, and had a login role, lets call it 'red', which had the superuser attribute assigned to it.   This was t

Re: [INTERNET] Re: auto vacuum question

On 8/28/23 16:11, Adrian Klaver wrote: > On 8/28/23 13:06, Alan Stange wrote: >> All, >> >> We recently changed the name of the superuser role in our database, and >> then noticed some issues with the autovacuum processes.  We are running >> 15.3, and had a login role, lets call it 'red', which had

Re: [INTERNET] Re: auto vacuum question

On 8/28/23 13:19, Alan Stange wrote: On 8/28/23 16:11, Adrian Klaver wrote: On 8/28/23 13:06, Alan Stange wrote: All, Are you sure that is coming from autovacuum? What are the log lines preceding the WARNING? What is the complete warning line? Thank you for your quick response. The pref

Re: auto vacuum question

Adrian Klaver writes: > On 8/28/23 13:06, Alan Stange wrote: > >> All, >> We recently changed the name of the superuser role in our database, My take on this, is that the *postmaster* user is perhaps the one that the OP cut privileges on, and thus the launcher is (now) spawning workers with less

Postgres service is not starting

The service was running fine, then I restarted the system and service was not starting. Force service restart says "service started and then stopped". In, Event Viewer, I found "pre existing memory block is still in use". I have tried restarting the service after deleting postmaster.pid and posgre

Re: Postgres service is not starting

On Monday, August 28, 2023, Vinit Saini wrote: > The service was running fine, then I restarted the system and service was > not starting. Force service restart says "service started and then > stopped". > In, Event Viewer, I found "pre existing memory block is still in use". > > I have tried res