I Use This!
Very High Activity

News

Analyzed about 2 hours ago. based on code collected about 3 hours ago.
Posted 7 months ago
SQLsmith has proven to be an effective tool for finding bugs in different areas in the PostgreSQL server and other products, including security bugs, ranging from executor bugs to segfaults in type and index method implementations. However, the ... [More] random queries generated by SQLsmith that trigger some error are most often very large and contain a lot of noise that does not contribute to the error. So far, manual inspection of the query and tedious editing was required to reduce the example to a minimal reproducer that developers can use to fix the problem. This issue is solved by SQLreduce. SQLreduce takes as input an arbitrary SQL query which is then run against a PostgreSQL server. Various simplification steps are applied, checking after each step that the simplified query still triggers the same error from PostgreSQL. The end result is a SQL query with minimal complexity. SQLreduce is effective at reducing the queries from original error reports from SQLsmith to queries that match manually-reduced queries. More details on how it works in a blog post. Example In 2018, SQLsmith found a segfault in PostgreSQL running Git revision 039eb6e92f. The reproducer back then was a huge 40-line, 2.2kB query: select case when pg_catalog.lastval() < pg_catalog.pg_stat_get_bgwriter_maxwritten_clean() then case when pg_catalog.circle_sub_pt( cast(cast(null as circle) as circle), cast((select location from public.emp limit 1 offset 13) as point)) ~ cast(nullif(case when cast(null as box) &> (select boxcol from public.brintest limit 1 offset 2) then (select f1 from public.circle_tbl limit 1 offset 4) else (select f1 from public.circle_tbl limit 1 offset 4) end, case when (select pg_catalog.max(class) from public.f_star) ~~ ref_0.c then cast(null as circle) else cast(null as circle) end ) as circle) then ref_0.a else ref_0.a end else case when pg_catalog.circle_sub_pt( cast(cast(null as circle) as circle), cast((select location from public.emp limit 1 offset 13) as point)) ~ cast(nullif(case when cast(null as box) &> (select boxcol from public.brintest limit 1 offset 2) then (select f1 from public.circle_tbl limit 1 offset 4) else (select f1 from public.circle_tbl limit 1 offset 4) end, case when (select pg_catalog.max(class) from public.f_star) ~~ ref_0.c then cast(null as circle) else cast(null as circle) end ) as circle) then ref_0.a else ref_0.a end end as c0, case when (select intervalcol from public.brintest limit 1 offset 1) >= cast(null as "interval") then case when ((select pg_catalog.max(roomno) from public.room) !~~ ref_0.c) and (cast(null as xid) <> 100) then ref_0.b else ref_0.b end else case when ((select pg_catalog.max(roomno) from public.room) !~~ ref_0.c) and (cast(null as xid) <> 100) then ref_0.b else ref_0.b end end as c1, ref_0.a as c2, (select a from public.idxpart1 limit 1 offset 5) as c3, ref_0.b as c4, pg_catalog.stddev( cast((select pg_catalog.sum(float4col) from public.brintest) as float4)) over (partition by ref_0.a,ref_0.b,ref_0.c order by ref_0.b) as c5, cast(nullif(ref_0.b, ref_0.a) as int4) as c6, ref_0.b as c7, ref_0.c as c8 from public.mlparted3 as ref_0 where true; SQLreduce can effectively reduce that monster to just this: SELECT pg_catalog.stddev(NULL) OVER () AS c5 FROM public.mlparted3 AS ref_0 Availability SQLreduce is open source licensed under the MIT license. The source code is on GitHub: https://github.com/credativ/sqlreduce Debian/Ubuntu packages for sqlreduce are shipped on apt.postgresql.org. SQLreduce is an open source product by credativ GmbH. [Less]
Posted 7 months ago
Hello PostgreSQL enthusiasts, We are proud to announce that Call for Papers for PGDay Austria 2022 is opened and due to that we are currently looking for exciting talks about PostgreSQL, whether in German or English. If you want to become a speaker ... [More] of PGDay Austria, feel free to submit a talk until the 30th of May 2022. We would be happy to welcome you in the beautiful location of Schloss Schönbrunn in Vienna! More information: https://pgday.at/en/talk-commitee/ Best regards, Anastasiya [Less]
Posted 7 months ago
We are happy to announce this year's edition of the Swiss PGDay to take place Friday, July 1 at the Eastern Switzerland University of Applied Sciences, Campus Rapperswil, close to Zurich, Switzerland. The conference will feature 1 day with two ... [More] tracks of presentations in English and German. The Call for Speakers is open now until 18.04.2022 23:59 CEST. Details can be found at https://pgday.ch/#tabs-2 Companies can use this unique opportunity to get in touch with the Swiss PostgreSQL community by sponsoring the event. Details on the Call for Sponsors can be found at https://pgday.ch/#tabs-5 Registration will open as soon as all details are set, expectedly mid March 2022. For continuously updated information about the Swiss PGDay 2022 visit: https://www.pgday.ch or register for the SwissPUG announce mailing list at https://www.swisspug.org/wiki/index.php/Contact Best regards, Swiss PGDay committee This is a community conference following the PostgreSQL Community Recognition Guidelines (https://www.postgresql.org/about/policies/conferences/). "PGDay" is a registered Trademark of PostgreSQL Europe, used with their permission. [Less]
Posted 7 months ago
Announcing the Belgian PostgreSQL Conference 2022 & Call for Papers PGConf.be 2022 is the sequel of the successful Belgian PostgreSQL conference 2019 in Haasrode, Leuven. The conference will take place on May 19th, 2022. Registration for the ... [More] conference will be opened later. The Call for Papers is open until March 30th. Submit your talks by mail with the subject 'I love Elephants'. The Call for Sponsors is open on https://pgconf.be See you in Leuven in May 2022! [Less]
Posted 7 months ago
dbMigration .NET v15.0 is a simple, easy and intuitive multiple database migration and sync tool, With it you can easily migrate and synchronize data to PostgreSQL and vice versa without complicated procedures. (Free for non-commercial and a single ... [More] executable file without installation) Major New features and improvements from version 14.5 to 15.0: Added support for PostgreSQL 8~14+, Amazone Redshift and YugabyteDB Added support for the timeonly data type Improved Bulk Insert mode Improved Filtering source data and Showing target data Improved user experience and user interface GetSchemaTable performance improvements Open Auto-generating FOREIGN KEYS of tables to all users Updated Npgsql.dll to 5.0.12 Updated the target .NET Framework to 4.7.2 ...and more The new version is immediately available for download. [Less]
Posted 7 months ago
The PostgreSQL Community Code of Conduct Committee is pleased to announce that the German translation of the Code of Conduct Policy updated August 18, 2020 has been posted: https://www.postgresql.org/about/policies/coc-translations/ The English ... [More] version of the Policy is at: https://www.postgresql.org/about/policies/coc/ The Committee thanks Andreas Scherbaum, Julian Markwort, Daniel Westermann, and Gunnar Bluth for their work in preparing the translation. Thanks also to Stefanie Janine Stölting and Andreas Kretschmer for additional proof-reading as well Karsten Hilbert for review and feedback. If you are interested in contributing a translation, the process overview is here. [Less]
Posted 7 months ago
pg_back is a tool that can dump all your databases to files, with the configuration of the server and roles/tablespaces definitions. The version 2.1.0 brings the following new features: Add quiet mode with the command line option -q/--quiet. It ... [More] takes precedence over verbose mode. Compute checksum of global and ACL files Add a dump of hba_file and ident_file Encrypt and decrypt produced files Upload files to AWS S3, Google Cloud Storage, Azure Blob Storage or a remote host with SFTP Add a systemd timer for Debian in the package generated by goreleaser Check the syntax of the configuration file And the following fixes: Always create a createdb.sql file for plain format instead of dumping with --create Ensure jobs option is greater than or equal to 1 Better check and adapt to versions of pg_dump and pg_dumpall Fix the purge based on a number of files to keep Improve the documentation in the README.md file pg_back is licensed under the classic 2 clauses BSD license. Thanks to all the contributors! More at https://github.com/orgrim/pg_back Binaries and packages are available on the github release page: https://github.com/orgrim/pg_back/releases/tag/v2.1.0 [Less]
Posted 8 months ago
What is Pgpool-II? Pgpool-II is a tool to add useful features to PostgreSQL, including: connection pooling load balancing automatic fail over and more. Minor releases Pgpool Global Development Group is pleased to announce the availability of ... [More] following versions of Pgpool-II: 4.3.1 4.2.8 4.1.11 4.0.18 3.7.23 Please take a look at release notes. You can download the source code and RPMs. [Less]
Posted 8 months ago
A security advisory has been created for the PostgreSQL JDBC Driver. The URL connection string loggerFile property could be mis-used to create an arbitrary file on the system that the driver is loaded. Additionally anything in the connection string ... [More] will be logged and subsequently written into that file. In an insecure system it would be possible to execute this file through a webserver. While we do not consider this a security issue with the driver, we have decided to remove the loggerFile and loggerLevel connection properties in the next release of the driver. Removal of those properties does not make exposing the JDBC URL or connection properties to an attacker safe and we continue to suggest that applications do not allow untrusted users to specify arbitrary connection properties. We are removing them to prevent misuse and their functionality can be delegated to java.util.logging. The changelog is not very useful as the change was done behind a security advisory. The short version is that loggerFile and loggerLevel properties still exist but do not do anything. The PostgreSQL JDBC team would like to thank all that have participated in this release! The JDBC Team [Less]
Posted 8 months ago
The PostgreSQL Community Code of Conduct Committee Annual Report for 2021 is now available at: https://www.postgresql.org/about/policies/coc/reports/2021/ All complaints, actions, and statistics are anonymized and aggregated to protect the ... [More] identities of all parties involved. You can contact the Committee with questions or comments by email: coc@postgresql.org Regards, Stefan Fercot PostgreSQL Community Code of Conduct Committee [Less]