connects - Search results in mailing lists
Mailing lists >> pgsql-bugs >> Thread
2025-05-20 16:07:47 | BUG #18936: Trigger enable users to modify the tables which he doesn't have privilege (PG Bug reporting form)
connected to database "test" as user "postgres". test=# create table t1(c0 int); CREATE TABLE
Mailing lists >> pgsql-bugs >> Thread
2025-05-20 09:40:15 | Re: BUG #18934: Even with WITH ADMIN OPTION, I Cannot Manage Role Memberships (Laurenz Albe)
connected to database "postgres" as user "postgres". CREATE ROLE a LOGIN; CREATE ROLE b ADMIN
Mailing lists >> pgsql-bugs >> Thread
2025-05-19 08:03:02 | Ge Yuxiang added you to the postgresql group (Ge Yuxiang)
connecting with everyone is easy.
Email the group
Mailing lists >> pgsql-bugs >> Thread
2025-05-14 15:37:36 | BUG #18928: postgres_fdw search_path not reset causing pgbouncer pool_mode=transaction using the (PG Bug reporting form)
connects to both in transaction pooling mode. See [pgbouncer.ini](https:///jackielii/pgbouncer-fdw-issue/blob/main/pgbouncer.ini) 3. connect to db2 via pgbouncer
Mailing lists >> pgsql-bugs >> Thread
2025-04-23 04:41:20 | RE: Disabled logical replication origin session causes primary key errors (Hayato Kuroda (Fujitsu))
connect to them - we can assume they are safe, OK to remove it. Opps, added
Mailing lists >> pgsql-bugs >> Thread
2025-04-21 17:56:43 | Re: Command order bug in pg_dump (Tom Lane)
connected to database "db1" as user "postgres". db1=# create table tfk (i int unique) partition
Mailing lists >> pgsql-bugs >> Thread
2025-04-17 03:09:09 | BUG #18898: replication process not working... sometimes (PG Bug reporting form)
connected to it, and the central pulls the aggregated data from the hubs). The up subscription
Mailing lists >> pgsql-bugs >> Thread
2025-04-12 06:34:59 | BUG #18893: Segfault during analyze pg_database (PG Bug reporting form)
reconnect to the database and repeat your command. server closed the connection unexpectedly This probably
Mailing lists >> pgsql-bugs >> Thread
2025-04-12 05:34:15 | BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether (PG Bug reporting form)
connected to database "test1" as user "postgres". test1=# create schema test; CREATE SCHEMA test1=# create
Mailing lists >> pgsql-bugs >> Thread
2025-04-08 17:32:03 | Re: BUG #18884: The CURRENT_TIMESTAMP value being returned in UTC-2. (Tom Lane)
program to connect to a different server with a different timezone setting. regards, tom lane
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (2)
2025-04-08 10:10:11 | BUG #18882: Unexpected write skew at SERIALIZABLE with psycopg2.connect() (PG Bug reporting form)
connect(**dbconfig) conn2 = psycopg2.connect(**dbconfig) cur1 = conn1.cursor() cur2 = conn2.cursor() try: cur1.execute
Mailing lists >> pgsql-bugs >> Thread
2025-04-08 08:50:56 | Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows (Laurenz Albe)
connect to that cluster, as the information is only in catalog tables. Also, if there
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (3)
2025-04-07 18:37:43 | Re: Re: Re: Revoke Connect Privilege from Database not working (David G. Johnston)
connect on database testdb:v to test_admin:v with grant option; set role test
Mailing lists >> pgsql-bugs >> Thread
2025-04-07 16:48:14 | Re: BUG #18880: Can't have a database without having postgres as a db_name (Tom Lane)
connect-to. I don't recommend deleting or renaming template0 or template1 under any circumstances
Mailing lists >> pgsql-bugs >> Thread
2025-03-26 01:05:55 | ltree gist index "incomplete split" (Wyatt Berlinic)
connect to the database and you will need to modify the connection string for your