Postgresql General Discussion
[Prev Page][Next Page]
- Fwd: PostGreSQL Replication and question on maintenance
- Re: Query which shows FK child columns?
- Query which shows FK child columns?
- Re: Wall shiping replica failed to recover database with error: invalid contrecord length 1956 at FED/38FFE208
- PostGreSQL Replication and question on maintenance
- Re: Postgresql RDS DB Latency Chossing Hash join Plan
- Re: Problems modifyiong view
- Re: Problems modifyiong view
- Re: Problems modifyiong view
- Re: Problems modifyiong view
- Re: Problems modifyiong view
- Re: INOUT PARAMETERS WITH RETURN TABLES IN FUNCTION
- Re: Problems modifyiong view
- RE: ERROR: COPY escape must be a single one-byte character (multi-delimiter appears to work on Postgres 9.0 but does not on Postgres 9.2)
- Re: Problems modifyiong view
- Re: Problems modifyiong view
- Re: Problems modifyiong view
- Problems modifyiong view
- Re: root page 3 of index "pg_class_oid_index" has level 0, expected 1
- Re: terminated by signal 11: Segmentation fault
- Re: root page 3 of index "pg_class_oid_index" has level 0, expected 1
- root page 3 of index "pg_class_oid_index" has level 0, expected 1
- Re: Wall shiping replica failed to recover database with error: invalid contrecord length 1956 at FED/38FFE208
- Re: `pg_ls_dir` can query some directories, but not others
- Re: ERROR: COPY escape must be a single one-byte character (multi-delimiter appears to work on Postgres 9.0 but does not on Postgres 9.2)
- ERROR: COPY escape must be a single one-byte character (multi-delimiter appears to work on Postgres 9.0 but does not on Postgres 9.2)
- Re: `pg_ls_dir` can query some directories, but not others
- `pg_ls_dir` can query some directories, but not others
- Re: Last autovacuum time - what is it?
- Re: terminated by signal 11: Segmentation fault
- Last autovacuum time - what is it?
- terminated by signal 11: Segmentation fault
- Re: CASE(?) to write in a different column based on a string pattern
- Re: CASE(?) to write in a different column based on a string pattern
- Re: CASE(?) to write in a different column based on a string pattern
- Re: CASE(?) to write in a different column based on a string pattern
- CASE(?) to write in a different column based on a string pattern
- Re: here does postgres take its timezone information from?
- Re: type SERIAL in C host-struct
- Re: here does postgres take its timezone information from?
- Sv: DELETE Query Hang
- From: Andreas Joseph Krogh
- Re: DELETE Query Hang
- Re: DELETE Query Hang
- Re: DELETE Query Hang
- DELETE Query Hang
- Re: here does postgres take its timezone information from?
- Re: security on user for replication
- From: Christoph Moench-Tegeder
- Re: Rules documentation example
- Rules documentation example
- Re: security on user for replication
- security on user for replication
- Partition, inheritance for storing syslog records.
- RE: Postgres Point in time Recovery (PITR),
- Re: announce: spark-postgres 3 released
- Re: How to import Apache parquet files?
- announce: spark-postgres 3 released
- Re: type SERIAL in C host-struct
- Re: type SERIAL in C host-struct
- Re: logical replication - negative bitmapset member not allowed
- From: Jehan-Guillaume de Rorthais
- Re: logical replication - negative bitmapset member not allowed
- Re: Storing a time interval
- Merge sort/postgis performance tweaking?
- Re: Storing a time interval
- Re: Storing a time interval
- Re: firewall trouble on Windows
- firewall trouble on Windows
- Re: Storing a time interval
- Re: Storing a time interval
- Re: Storing a time interval
- pg_logical for RHEL 8
- Storing a time interval
- Re: AW: AW: AW: AW: AW: AW: AW: broken backup trail in case of quickly patroni switchback and forth
- AW: AW: AW: AW: AW: AW: AW: broken backup trail in case of quickly patroni switchback and forth
- From: Zwettler Markus (OIZ)
- Re: AW: AW: AW: AW: AW: AW: broken backup trail in case of quickly patroni switchback and forth
- AW: AW: AW: AW: AW: AW: broken backup trail in case of quickly patroni switchback and forth
- From: Zwettler Markus (OIZ)
- Re: AW: AW: AW: AW: AW: broken backup trail in case of quickly patroni switchback and forth
- AW: AW: AW: AW: AW: broken backup trail in case of quickly patroni switchback and forth
- From: Zwettler Markus (OIZ)
- Re: INOUT PARAMETERS WITH RETURN TABLES IN FUNCTION
- Re: AW: AW: AW: AW: broken backup trail in case of quickly patroni switchback and forth
- Re: SQL SERVER migration to PostgreSql
- AW: AW: AW: AW: broken backup trail in case of quickly patroni switchback and forth
- From: Zwettler Markus (OIZ)
- Re: INOUT PARAMETERS WITH RETURN TABLES IN FUNCTION
- INOUT PARAMETERS WITH RETURN TABLES IN FUNCTION
- AW: broken backup trail in case of quickly patroni switchback and forth
- From: Zwettler Markus (OIZ)
- Re: logging proxy
- Re: type SERIAL in C host-struct
- Re: AW: AW: AW: broken backup trail in case of quickly patroni switchback and forth
- Re: broken backup trail in case of quickly patroni switchback and forth
- AW: AW: AW: broken backup trail in case of quickly patroni switchback and forth
- From: Zwettler Markus (OIZ)
- Re: 11 -> 12 upgrade on Debian Ubuntu
- Re: AW: AW: broken backup trail in case of quickly patroni switchback and forth
- Re: 11 -> 12 upgrade on Debian Ubuntu
- Re: 11 -> 12 upgrade on Debian Ubuntu
- Re: 11 -> 12 upgrade on Debian Ubuntu
- AW: AW: broken backup trail in case of quickly patroni switchback and forth
- From: Zwettler Markus (OIZ)
- 11 -> 12 upgrade on Debian Ubuntu
- Re: AW: broken backup trail in case of quickly patroni switchback and forth
- AW: broken backup trail in case of quickly patroni switchback and forth
- From: Zwettler Markus (OIZ)
- Re: logical replication - negative bitmapset member not allowed
- From: Jehan-Guillaume de Rorthais
- Re: SQL SERVER migration to PostgreSql
- Re: broken backup trail in case of quickly patroni switchback and forth
- Re: logical replication - negative bitmapset member not allowed
- Re: SQL SERVER migration to PostgreSql
- Re: logical replication - negative bitmapset member not allowed
- SQL SERVER migration to PostgreSql
- broken backup trail in case of quickly patroni switchback and forth
- From: Zwettler Markus (OIZ)
- Re: PostgreSQL && data types in ESQL/C
- type SERIAL in C host-struct
- Re: Hunspell as filtering dictionary
- Re: Locked out of schema public (pg_dump lacks backup of the grant)
- Re: Locked out of schema public
- Re: Locked out of schema public (pg_dump lacks backup of the grant)
- Re: Locked out of schema public (pg_dump lacks backup of the grant)
- How to convert return values from JSON Path functions to text
- Re: Locked out of schema public
- Locked out of schema public
- Re: Upgrade PGSQL main version without backup/restore all databases?
- Re: Hunspell as filtering dictionary
- Re: Upgrade PGSQL main version without backup/restore all databases?
- Upgrade PGSQL main version without backup/restore all databases?
- Re: Vacuum very big table - how the full vacuum works in background/internally?
- Re: PostgreSQL && data types in ESQL/C
- PostgreSQL && data types in ESQL/C
- Re: here does postgres take its timezone information from?
- Re: here does postgres take its timezone information from?
- Re: here does postgres take its timezone information from?
- Re: here does postgres take its timezone information from?
- Re: here does postgres take its timezone information from?
- Re: here does postgres take its timezone information from?
- Re: here does postgres take its timezone information from?
- here does postgres take its timezone information from?
- RE: Upgrade procedure
- Re: select view definition from pg_views feature request
- Re: Upgrade procedure
- RE: Upgrade procedure
- RE: Upgrade procedure
- Re: logical replication - negative bitmapset member not allowed
- Re: How to import Apache parquet files?
- Re: logical replication - negative bitmapset member not allowed
- From: Jehan-Guillaume de Rorthais
- Re: select view definition from pg_views feature request
- Re: How to import Apache parquet files?
- Re: How to import Apache parquet files?
- Re: logical replication - negative bitmapset member not allowed
- Re: select view definition from pg_views feature request
- How to import Apache parquet files?
- Re: select view definition from pg_views feature request
- Hunspell as filtering dictionary
- Re: Create a logical and physical replication
- From: Andreas Joseph Krogh
- Re: Create a logical and physical replication
- Re: Create a logical and physical replication
- Re: Create a logical and physical replication
- Re: select view definition from pg_views feature request
- Re: select view definition from pg_views feature request
- Re: question about array indexing
- question about array indexing
- Re: explain plan difference
- Re: explain plan difference
- Re: explain plan difference
- Re: explain plan difference
- Re: select view definition from pg_views feature request
- Create a logical and physical replication
- Re: explain plan difference
- Re: Are my autovacuum settings too aggressive for this table?
- Re: explain plan difference
- Re: explain plan difference
- explain plan difference
- Re: select view definition from pg_views feature request
- select view definition from pg_views feature request
- Re: Getting following error in using cursor to fetch the records from a large table in c language(current transaction is aborted, commands ignored until end of transaction block)
- Re: Can you please suggest how to configure hot_standby_feedback?
- From: Nikolay Samokhvalov
- Re: Can you please suggest how to configure hot_standby_feedback?
- From: Konstantin Gredeskoul
- RE: Getting following error in using cursor to fetch the records from a large table in c language(current transaction is aborted, commands ignored until end of transaction block)
- Re: QUERY: autovacuum: VACUUM ANALYZE table versus QUERY: autovacuum: VACUUM table
- Re: QUERY: autovacuum: VACUUM ANALYZE table versus QUERY: autovacuum: VACUUM table
- QUERY: autovacuum: VACUUM ANALYZE table versus QUERY: autovacuum: VACUUM table
- RE: Declarative Range Partitioning Postgres 11
- RE: Are my autovacuum settings too aggressive for this table?
- Re: Are my autovacuum settings too aggressive for this table?
- Re: Declarative Range Partitioning Postgres 11
- Are my autovacuum settings too aggressive for this table?
- Re: Getting following error in using cursor to fetch the records from a large table in c language(current transaction is aborted, commands ignored until end of transaction block)
- RE: Declarative Range Partitioning Postgres 11
- Getting following error in using cursor to fetch the records from a large table in c language(current transaction is aborted, commands ignored until end of transaction block)
- RE: Barman
- RE: Getting following error in using cursor to fetch the records from a large table in c language
- logging proxy
- Re: Getting following error in using cursor to fetch the records from a large table in c language
- Re: Barman
- Barman
- Re: Automatically parsing in-line composite types
- Re: Automatically parsing in-line composite types
- Re: Automatically parsing in-line composite types
- Re: Can you please suggest how to configure hot_standby_feedback?
- RE: Getting following error in using cursor to fetch the records from a large table in c language
- Re: Getting following error in using cursor to fetch the records from a large table in c language
- Re: Upgrade procedure
- Can you please suggest how to configure hot_standby_feedback?
- RE: Getting following error in using cursor to fetch the records from a large table in c language
- Re: Automatically parsing in-line composite types
- RE: Upgrade procedure
- Re: Automatically parsing in-line composite types
- Re: Automatically parsing in-line composite types
- Re: Getting following error in using cursor to fetch the records from a large table in c language
- Re: Upgrade procedure
- Getting following error in using cursor to fetch the records from a large table in c language
- Upgrade procedure
- Re: Automatically parsing in-line composite types
- From: Fabio Ugo Venchiarutti
- Re: Automatically parsing in-line composite types
- Re: Automatically parsing in-line composite types
- Re: Restore single table
- Restore single table
- Re: Automatically parsing in-line composite types
- Re: Automatically parsing in-line composite types
- Re: Automatically parsing in-line composite types
- Re: Automatically parsing in-line composite types
- Re: Automatically parsing in-line composite types
- From: Fabio Ugo Venchiarutti
- Re: Automatically parsing in-line composite types
- Re: PostgreSQL - unrecognized win32 error code: 38
- Re: PostgreSQL - unrecognized win32 error code: 38
- Re: PostgreSQL - unrecognized win32 error code: 38
- Re: SQL pretty pritner?
- Re: SQL pretty pritner?
- Re: PostgreSQL - unrecognized win32 error code: 38
- Re: SQL pretty pritner?
- RE: SQL pretty pritner?
- Re: I think that my data is saved correctly, but when printing again, other data appears
- Re: jsonb_set() strictness considered harmful to data
- Re: SQL pretty pritner?
- From: Basques, Bob (CI-StPaul)
- Re: SQL pretty pritner?
- From: Basques, Bob (CI-StPaul)
- Re: jsonb_set() strictness considered harmful to data
- Re: SQL pretty pritner?
- Re: SQL pretty pritner?
- Re: SQL pretty pritner?
- Re: SQL pretty pritner?
- Re: SQL pretty pritner?
- From: Basques, Bob (CI-StPaul)
- Re: I think that my data is saved correctly, but when printing again, other data appears
- Re: I think that my data is saved correctly, but when printing again, other data appears
- Re: SQL pretty pritner?
- Re: I think that my data is saved correctly, but when printing again, other data appears
- SQL pretty pritner?
- Re: I think that my data is saved correctly, but when printing again, other data appears
- Re: Installation problem.
- Installation problem.
- Re: PostgreSQL - unrecognized win32 error code: 38
- Re: PostgreSQL - unrecognized win32 error code: 38
- Re: Updating data: confirmation and question
- Re: Updating data: confirmation and question
- Re: I think that my data is saved correctly, but when printing again, other data appears
- Re: Updating data: confirmation and question
- Re: Updating data: confirmation and question
- Re: PostgreSQL - unrecognized win32 error code: 38
- PostgreSQL - unrecognized win32 error code: 38
- Re: Updating data: confirmation and question
- Re: Updating data: confirmation and question
- Updating data: confirmation and question
- Re: Composite type storage overhead
- Re: I think that my data is saved correctly, but when printing again, other data appears
- Re: Trying to fetch records only if preceded by at least another one
- Re: Trying to fetch records only if preceded by at least another one
- Re: Composite type storage overhead
- Re: Quere keep using temporary files
- Re: Trying to fetch records only if preceded by at least another one
- Re: Quere keep using temporary files
- Re: logical replication - negative bitmapset member not allowed
- From: Jehan-Guillaume de Rorthais
- Re: I think that my data is saved correctly, but when printing again, other data appears
- Trying to fetch records only if preceded by at least another one
- Re: I think that my data is saved correctly, but when printing again, other data appears
- Re: Error building Postgres for Windows
- Re: Quere keep using temporary files
- I think that my data is saved correctly, but when printing again, other data appears
- Re: Index
- Re: Index
- Re: Quere keep using temporary files
- Error building Postgres for Windows
- Quere keep using temporary files
- Re: Search path
- Index
- Re: Is this a bug ?
- Re: jsonb_set() strictness considered harmful to data
- Re: EXPLAIN BUFFERS and I/O timing accounting questions
- Re: EXPLAIN BUFFERS and I/O timing accounting questions
- Re: A very puzzling backup/restore problem
- Re: A very puzzling backup/restore problem
- Re: A very puzzling backup/restore problem
- Re: EXPLAIN BUFFERS and I/O timing accounting questions
- Re: jsonb_set() strictness considered harmful to data
- Re: SQL Error [0A000]: ERROR: nondeterministic collations are not supported for LIKE
- Re: SQL Error [0A000]: ERROR: nondeterministic collations are not supported for LIKE
- Re: jsonb_set() strictness considered harmful to data
- Re: Recover databases from raw files (only exists the base directory)
- Re: Lookup Primary Key of Foreign Server's Table
- Recover databases from raw files (only exists the base directory)
- Re: Search path
- Search path
- Re: Having more than one constraint trigger on a table
- From: Andreas Joseph Krogh
- SQL Error [0A000]: ERROR: nondeterministic collations are not supported for LIKE
- Re: Having more than one constraint trigger on a table
- Re: LocalTransactionId vs txid_current
- Re: A very puzzling backup/restore problem
- Re: A very puzzling backup/restore problem
- Re: PGPool version 4.0.6-1
- Re: A very puzzling backup/restore problem
- Re: A very puzzling backup/restore problem
- LocalTransactionId vs txid_current
- PGPool version 4.0.6-1
- A very puzzling backup/restore problem
- Re: Composite type storage overhead
- Failed to increase the restart LSN of PostgreSQL logical replication slot
- Re: Composite type storage overhead
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: Composite type storage overhead
- Re: Composite type storage overhead
- Re: Composite type storage overhead
- Composite type storage overhead
- Re: Is this a bug ?
- Re: Automatically parsing in-line composite types
- Re: Is this a bug ?
- Re: Is this a bug ?
- Re: Is this a bug ?
- Re: jsonb_set() strictness considered harmful to data
- Re: Is this a bug ?
- Re: jsonb_set() strictness considered harmful to data
- Re: Is this a bug ?
- From: Fabio Ugo Venchiarutti
- Re: Is this a bug ?
- Re: date function bug
- Re: Is this a bug ?
- Re: Is this a bug ?
- Re: Is this a bug ?
- Re: Is this a bug ?
- Re: EXPLAIN BUFFERS and I/O timing accounting questions
- Re: Lookup Primary Key of Foreign Server's Table
- Re: Is this a bug ?
- Re: Is this a bug ?
- Re: jsonb_set() strictness considered harmful to data
- Re: Is this a bug ?
- Re: Is this a bug ?
- Re: Is this a bug ?
- From: Fabio Ugo Venchiarutti
- Re: Is this a bug ?
- Re: Is this a bug ?
- Re: Is this a bug ?
- Re: Is this a bug ?
- Re: Is this a bug ?
- Re: Lookup Primary Key of Foreign Server's Table
- Re: Is this a bug ?
- Is this a bug ?
- Re: Calling jsonb_array_elements 4 times in the same query
- Re: date function bug
- Re: date function bug
- Re: date function bug
- RE: date function bug
- Re: date function bug
- RE: Re: date function bug
- Re: date function bug
- Re: date function bug
- Re: date function bug
- date function bug
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: Upgrade mode will prevent the installer .... (pgAgent)
- Upgrade mode will prevent the installer .... (pgAgent)
- Re: A question about sequences and backup/restore cycles
- Re: Primary key definition?
- SQL Error [0A000]: ERROR: nondeterministic collations are not supported for LIKE
- Re: A question about sequences and backup/restore cycles
- Re: A question about sequences and backup/restore cycles
- Re: Primary key definition?
- Re: Primary key definition?
- Re: A question about sequences and backup/restore cycles
- Primary key definition?
- Re: Recovering disk space
- Re: Regarding db dump with Fc taking very long time to completion
- Re: An issue installing an extension
- An issue installing an extension
- Re: Lookup Primary Key of Foreign Server's Table
- Lookup Primary Key of Foreign Server's Table
- Re: existing dblinks
- Re: Having more than one constraint trigger on a table
- From: Andreas Joseph Krogh
- Re: Having more than one constraint trigger on a table
- Having more than one constraint trigger on a table
- From: Andreas Joseph Krogh
- Re: FW: Re: A question about building pg-libphonenumber
- FW: Re: A question about building pg-libphonenumber
- Re: A question about building pg-libphonenumber
- Re: pg_hba & ldap
- Re: A question about building pg-libphonenumber
- Re: A question about building pg-libphonenumber
- A question about building pg-libphonenumber
- pg_hba & ldap
- A question about sequnces and pg_restore
- Re: Too many SET TimeZone and Application_name queries
- EXPLAIN BUFFERS and I/O timing accounting questions
- Re: A question about sequences and backup/restore cycles
- A question about sequences and backup/restore cycles
- existing dblinks
- Re: jsonb_set() strictness considered harmful to data
- Re: Calling jsonb_array_elements 4 times in the same query
- Re: jsonb_set() strictness considered harmful to data
- Re: Calling jsonb_array_elements 4 times in the same query
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: CPU SPIKE
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: Postgres Point in time Recovery (PITR),
- Re: Postgres Point in time Recovery (PITR),
- Re: Postgres Point in time Recovery (PITR),
- Re: Postgres Point in time Recovery (PITR),
- Re: Postgres Point in time Recovery (PITR),
- Re: jsonb_set() strictness considered harmful to data
- Re: Postgres Point in time Recovery (PITR),
- Re: Calling jsonb_array_elements 4 times in the same query
- Re: Calling jsonb_array_elements 4 times in the same query
- Re: Calling jsonb_array_elements 4 times in the same query
- Re: Calling jsonb_array_elements 4 times in the same query
- Calling jsonb_array_elements 4 times in the same query
- Re: jsonb_set() strictness considered harmful to data
- Re: Postgres Point in time Recovery (PITR),
- From: Fabio Ugo Venchiarutti
- Re: Postgres Point in time Recovery (PITR),
- Re: Postgres Point in time Recovery (PITR),
- From: Fabio Ugo Venchiarutti
- Re: Postgres Point in time Recovery (PITR),
- Re: jsonb_set() strictness considered harmful to data
- Re: CPU SPIKE
- Re: CPU SPIKE
- CPU SPIKE
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: Too many SET TimeZone and Application_name queries
- Re: jsonb_set() strictness considered harmful to data
- Re: UTC-6 or UTC+6?
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- UTC-6 or UTC+6?
- Re: jsonb_set() strictness considered harmful to data
- jsonb_set() strictness considered harmful to data
- Re: releasing space
- Re: releasing space
- Re: releasing space
- Re: releasing space
- Re: Execute a function through fdw
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: Postgres Point in time Recovery (PITR),
- Re: Postgres Point in time Recovery (PITR),
- Re: jsonb_set() strictness considered harmful to data
- RE: Postgres Point in time Recovery (PITR),
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- From: Christoph Moench-Tegeder
- Re: jsonb_set() strictness considered harmful to data
- Re: Has there been any discussion of custom dictionaries being defined in the database?
- Re: releasing space
- Re: Replication of Replication
- Re: Securing records using linux grou permissions
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- From: Christoph Moench-Tegeder
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Re: jsonb_set() strictness considered harmful to data
- Replication of Replication
- Re: jsonb_set() strictness considered harmful to data
- From: Christoph Moench-Tegeder
- Re: jsonb_set() strictness considered harmful to data
- jsonb_set() strictness considered harmful to data
- RE: Execute a function through fdw
- Re: Execute a function through fdw
- RE: Execute a function through fdw
- Re: DBD::Pg exorts char columns with trailing blanks
- Re: DBD::Pg exorts char columns with trailing blanks
- Re: DBD::Pg exorts char columns with trailing blanks
- Re: DBD::Pg exorts char columns with trailing blanks
- Re: DBD::Pg exorts char columns with trailing blanks
- Re: connection timeout with psycopg2
- RE: CVE-2018-1058
- From: Lizeth Solis Aramayo
- Re: DBD::Pg exorts char columns with trailing blanks
- Visibility Map Issues
- RE: Execute a function through fdw
- DBD::Pg exorts char columns with trailing blanks
- Re: Postgres Point in time Recovery (PITR),
- Re: Execute a function through fdw
- Re: Create role like role
- Re: Postgres Point in time Recovery (PITR),
- Re: stable for each row before insert trigger
- Re: Execute a function through fdw
- Create role like role
- Execute a function through fdw
- Re: Postgres Point in time Recovery (PITR),
- Re: stable for each row before insert trigger
- Re: Sv: Conflict between autovacuum and backup restoration
- Re: Postgres Point in time Recovery (PITR),
- Sv: Postgres Point in time Recovery (PITR),
- From: Andreas Joseph Krogh
- Re: Postgres Point in time Recovery (PITR),
- Re: Postgres Point in time Recovery (PITR),
- Re: stable for each row before insert trigger
- Re: stable for each row before insert trigger
- Re: A little confusion about JSON Path
- Re: stable for each row before insert trigger
- Postgres Point in time Recovery (PITR),
- Can you please tell us how set this prefetch attribute in following lines.
- Re:Using PostgreSQL for Machine Learning Data Pipelines
- Re: drop database
- Re: stable for each row before insert trigger
- stable for each row before insert trigger
- Re: drop database
- Re: drop database
- Re: drop database
- Re: drop database
- Re: drop database
- Re: Sv: drop database
- Sv: drop database
- From: Andreas Joseph Krogh
- Re: drop database
- Sv: drop database
- From: Andreas Joseph Krogh
- drop database
- Re: Changing PK on replicated database
- Re: releasing space
- Re: Vacuum very big table - how the full vacuum works in background/internally?
- Using PostgreSQL for Machine Learning Data Pipelines
- releasing space
- Re: Can you please tell us how set this prefetch attribute in following lines.
- Re: Can you please tell us how set this prefetch attribute in following lines.
- Re: Vacuum very big table - how the full vacuum works in background/internally?
- Vacuum very big table - how the full vacuum works in background/internally?
- Re: Changing PK on replicated database
- RE: CVE-2018-1058
- From: Lizeth Solis Aramayo
- Re: CVE-2018-1058
- Sv: Conflict between autovacuum and backup restoration
- From: Andreas Joseph Krogh
- Conflict between autovacuum and backup restoration
- Re: Can functions containing a CTE be PARALLEL SAFE?
- Re: PostgreSQL memory usage
- RE: PostgreSQL memory usage
- Re: A little confusion about JSON Path
- Re: PostgreSQL memory usage
- Re: pgbackrest with PAF(corosync and pacmaker)
- Re: Has there been any discussion of custom dictionaries being defined in the database?
- Re: Changing PK on replicated database
- Re: Has there been any discussion of custom dictionaries being defined in the database?
- pgbackrest with PAF(corosync and pacmaker)
- Re: Pgbackrest backup is too slow
- Re: Has there been any discussion of custom dictionaries being defined in the database?
- Re: Has there been any discussion of custom dictionaries being defined in the database?
- Re: Can functions containing a CTE be PARALLEL SAFE?
- Re: Has there been any discussion of custom dictionaries being defined in the database?
- Has there been any discussion of custom dictionaries being defined in the database?
- Re: PostgreSQL memory usage
- Can functions containing a CTE be PARALLEL SAFE?
- Re: CVE-2018-1058
- Re: Changing PK on replicated database
- Re: CVE-2018-1058
- Re: CVE-2018-1058
- Re: CVE-2018-1058
- RE: CVE-2018-1058
- From: Lizeth Solis Aramayo
- Re: CVE-2018-1058
- Changing PK on replicated database
- Re: CVE-2018-1058
- Re: CVE-2018-1058
- Re: CVE-2018-1058
- CVE-2018-1058
- From: Lizeth Solis Aramayo
- Text search lexer's handling of hyphens and negatives
- RE: Postgres 10.7 Systemd Startup Issue
- RE: Postgres 10.7 Systemd Startup Issue
- Re: Postgres 9.6 active-passive HA cluster
- PostgreSQL memory usage
- Re: Text search lexer's handling of hyphens and negatives
- Re: Analyze and vaccum
- Analyze and vaccum
- Re: Regarding db dump with Fc taking very long time to completion
- A little confusion about JSON Path
- Re: Text search lexer's handling of hyphens and negatives
- Re: Is there any configuration in postgresql.conf or any other configuration of postgres which will make this possible to listen on particular interface
- Postgres 9.6 active-passive HA cluster
- Is there any configuration in postgresql.conf or any other configuration of postgres which will make this possible to listen on particular interface
- Re: Regarding db dump with Fc taking very long time to completion
- Re: Regarding db dump with Fc taking very long time to completion
- Re: Regarding db dump with Fc taking very long time to completion
- connection timeout with psycopg2
- From: Vicente Juan Tomas Monserrat
- Re: Regarding db dump with Fc taking very long time to completion
- Re: Securing records using linux grou permissions
- Re: Text search lexer's handling of hyphens and negatives
- Re: Text search lexer's handling of hyphens and negatives
- Text search lexer's handling of hyphens and negatives
- Re: Securing records using linux grou permissions
- Re: Securing records using linux grou permissions
- Re: Securing records using linux grou permissions
- Securing records using linux grou permissions
- Re: SELECT returnig a constant
- Re: Pg11 -- MultiXactId xxxx has not been created yet -- apparent wraparound
- Re: Inserting multiple rows wtih a SELECt in the values clause
- Re: SELECT returnig a constant
- Inserting multiple rows wtih a SELECt in the values clause
- Re: timescaleDB & WAL replication
- SOLVED Re: SELECT returnig a constant
- SELECT returnig a constant
- Re: How to make runtime partition pruning work?
- timescaleDB & WAL replication
- Re: How to make runtime partition pruning work?
- Re: Too many SET TimeZone and Application_name queries
- Re: Postgres 10.7 Systemd Startup Issue
- Re: Too many SET TimeZone and Application_name queries
- Re: day interval
- RE: Re: day interval
- Re: day interval
- Re: SELECT d02name::bytea FROM ... && DBI::Pg
- Re: day interval
- Re: day interval
- RE: Re: day interval
- Re: day interval
- RE: Re: day interval
- Re: day interval
- Re: day interval
- RE: Re: day interval
- Re: day interval
- day interval
- Re: Perl DBI converts UTF-8 again to UTF-8 before sending it to the server
- Re: SELECT d02name::bytea FROM ... && DBI::Pg
- From: Christoph Moench-Tegeder
- Re: Case Insensitive Comparison with Postgres 12
- Re: Perl DBI converts UTF-8 again to UTF-8 before sending it to the server
- From: Christoph Moench-Tegeder
- Re: Segmentation fault with PG-12
- From: Andreas Joseph Krogh
- Re: SELECT d02name::bytea FROM ... && DBI::Pg
- Re: got error: DELETE FROM planet_osm_line WHERE osm_id = -390840 failed: FEHLER: tuple concurrently updated
- Re: got error: DELETE FROM planet_osm_line WHERE osm_id = -390840 failed: FEHLER: tuple concurrently updated
- Re: got error: DELETE FROM planet_osm_line WHERE osm_id = -390840 failed: FEHLER: tuple concurrently updated
- Re: got error: DELETE FROM planet_osm_line WHERE osm_id = -390840 failed: FEHLER: tuple concurrently updated
- Re: got error: DELETE FROM planet_osm_line WHERE osm_id = -390840 failed: FEHLER: tuple concurrently updated
- Re: got error: DELETE FROM planet_osm_line WHERE osm_id = -390840 failed: FEHLER: tuple concurrently updated
- got error: DELETE FROM planet_osm_line WHERE osm_id = -390840 failed: FEHLER: tuple concurrently updated
- Re: how can I get non-truncated version of running sql?
- how can I get non-truncated version of running sql?
- Profile a db connection time?
- Re: Case Insensitive Comparison with Postgres 12
- Re: Pgbackrest backup is too slow
- Re: JSON vs. JSONB storage size
- Re: JSON vs. JSONB storage size
- Re: JSON vs. JSONB storage size
- Re: Issues with PAM : log that it failed, whether it actually failed or not
- Re: Perl DBI converts UTF-8 again to UTF-8 before sending it to the server
- Re: Too many SET TimeZone and Application_name queries
- Re: Pgbackrest backup is too slow
- Re: Pgbackrest backup is too slow
- Re: Trigger
- From: Charles Clavadetscher
- Too many SET TimeZone and Application_name queries
- JSON vs. JSONB storage size
- Trigger
- Pgbackrest backup is too slow
- How to make runtime partition pruning work?
- Issues with PAM : log that it failed, whether it actually failed or not
- From: La Cancellera Yoann
- Re: DDL support for logical replication
- Re: DDL support for logical replication
- Re: Is my lecturer wrong about PostgreSQL? I think he is!
- Re: Segmentation fault with PG-12
- Re: DDL support for logical replication
- Re: The connection to the server was lost. Attempting reset: Failed.
- Re: DDL support for logical replication
- Re: plpgsql copy import csv double quotes
- Re: Segmentation fault with PG-12
- From: Andreas Joseph Krogh
- Re: The connection to the server was lost. Attempting reset: Failed.
- Re: Segmentation fault with PG-12
- Re: plpgsql copy import csv double quotes
- Re: The connection to the server was lost. Attempting reset: Failed.
- Re: The connection to the server was lost. Attempting reset: Failed.
- DDL support for logical replication
- Re: The connection to the server was lost. Attempting reset: Failed.
- Re: SELECT d02name::bytea FROM ... && DBI::Pg
- Re: SELECT d02name::bytea FROM ... && DBI::Pg
- Re: The connection to the server was lost. Attempting reset: Failed.
- Re: The connection to the server was lost. Attempting reset: Failed.
- Re: The connection to the server was lost. Attempting reset: Failed.
- Re: The connection to the server was lost. Attempting reset: Failed.
- The connection to the server was lost. Attempting reset: Failed.
- Re: Case Insensitive Comparison with Postgres 12
- RE: plpgsql copy import csv double quotes
- Re: Minimum privilege for Backup and replication
- Re: Event Triggers and GRANT/REVOKE
- Re: SOLVED Re: Recovering disk space
- Re: psql \copy hanging
- Re: Is my lecturer wrong about PostgreSQL? I think he is!
- websearch_to_tsquery() and handling of ampersand characters inside double quotes
- Re: websearch_to_tsquery() and apostrophe inside double quotes
- Re: syntax error with v12
- Re: syntax error with v12
- Re: websearch_to_tsquery() and apostrophe inside double quotes
- Re: Case Insensitive Comparison with Postgres 12
- Re: logical replication - negative bitmapset member not allowed
- From: Jehan-Guillaume de Rorthais
- Re: syntax error with v12
- Re: syntax error with v12
- syntax error with v12
- Re: Case Insensitive Comparison with Postgres 12
- Re: Minimum privilege for Backup and replication
- websearch_to_tsquery() and apostrophe inside double quotes
- Minimum privilege for Backup and replication
- SELECT d02name::bytea FROM ... && DBI::Pg
- Re: Is my lecturer wrong about PostgreSQL? I think he is!
- Re: Segmentation fault with PG-12
- From: Andreas Joseph Krogh
- Re: Is my lecturer wrong about PostgreSQL? I think he is!
- Re: Version 10.7 of postgres
- Re: Is my lecturer wrong about PostgreSQL? I think he is!
- SOLVED Re: Recovering disk space
- Recovering disk space
- Re: Segmentation fault with PG-12
- Re: Segmentation fault with PG-12
- From: Andreas Joseph Krogh
- Re: psql \copy hanging
- Re: Version 10.7 of postgres
- Re: Segmentation fault with PG-12
- Version 10.7 of postgres
- Re: pgutils, pglogger and pgutilsL out
- pgutils, pglogger and pgutilsL out
- Re: plpgsql copy import csv double quotes
- Re: Is my lecturer wrong about PostgreSQL? I think he is!
- Re: Event Triggers and GRANT/REVOKE
- Re: Event Triggers and GRANT/REVOKE
- Re: plpgsql copy import csv double quotes
- plpgsql copy import csv double quotes
- Event Triggers and GRANT/REVOKE
- Re: Allowing client access
- Re: Is my lecturer wrong about PostgreSQL? I think he is!
- Re: Is my lecturer wrong about PostgreSQL? I think he is!
- Re: Is my lecturer wrong about PostgreSQL? I think he is!
- Re: I messed up and my disk utlization is HUGE
- Is my lecturer wrong about PostgreSQL? I think he is!
- Re: Allowing client access
- Re: Pg11 -- MultiXactId xxxx has not been created yet -- apparent wraparound
- I messed up and my disk utlization is HUGE
- Repmgr and pglogical
- Re: Segmentation fault with PG-12
- Re: Segmentation fault with PG-12
- From: Andreas Joseph Krogh
- Re: Segmentation fault with PG-12
- Re: GSSAPI: logging principal
- Re: Allowing client access
- Allowing client access
- Re: Event Triggers and Dropping Objects
- Re: Segmentation fault with PG-12
- From: Andreas Joseph Krogh
- GSSAPI: logging principal
- Re: Case Insensitive Comparison with Postgres 12
- Re: Case Insensitive Comparison with Postgres 12
- Re: Case Insensitive Comparison with Postgres 12
- Transition tables for column-specific UPDATE triggers
- Re: Case Insensitive Comparison with Postgres 12
- Case Insensitive Comparison with Postgres 12
- Re: Declarative Range Partitioning Postgres 11
- RE: Declarative Range Partitioning Postgres 11
- Re: Segmentation fault with PG-12
- From: Andreas Joseph Krogh
- Re: Declarative Range Partitioning Postgres 11
- Re: Declarative Range Partitioning Postgres 11
- Re: temporary files
- Re: Segmentation fault with PG-12
- Segmentation fault with PG-12
- From: Andreas Joseph Krogh
- Re: Table locking during backup
- Re: psql \copy hanging
- Re: psql \copy hanging
- Re: psql \copy hanging
- RE: Declarative Range Partitioning Postgres 11
- RE: Declarative Range Partitioning Postgres 11
[Index of Archives]
[Postgresql Jobs]
[Postgresql Admin]
[Postgresql Performance]
[PHP Home]
[PHP on Windows]
[Yosemite]