summaryrefslogtreecommitdiff
path: root/databases (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* databases/percona-toolkit: Update to 3.3.1Florian Smeets2022-02-202-6/+10
|
* databases/mariadb106-server: Add MariaDB 10.6 to portsBernard Spil2022-02-2018-0/+1322
| | | | | PR: Reported by: Vincent Milum Jr <freebsd darkain com>
* devel/ruby-gems: Update to 3.3.7Dan Langille2022-02-201-10/+10
| | | | | | | | | | | | | | | | | | | | These are fixes Ruby 3.0 Changes were compiled against all dependencies of devel/ruby-gems and they all built cleanly. There are five known build failures, all prexisting: * devel/rubygem-xdg5: requires Ruby 3.0 * devel/rubygem-xdg: requires Ruby 3.1 * graphics/rubygem-objectdetect: port explicitly marked broken * mail/rubygem-tmail: port explicitly marked broken * science/cdcl: marked broken, unfetchable Plus, science/rubygem-ruby-dcl gets skipped because of science/cdcl PR: 258108 Approved by: ruby (zi@)
* databases/cego: upgrade 2.47.16 -> 2.47.22Björn Lemke2022-02-202-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Fix in CegoFunction::clone, also if _exprList is empty, the function must treated and cloned completely including table manager reference. Otherwise, for user defined function with no arguments which are used in views will throw an exception - Change in CegoJDBCInfo for table list retrievel. This JDBC meta information command is not split to tab and vie for dedicated retrievel of table and view objects - More work has been done regarding clean shutdown of the database / tableset stop while busy db sessions still exist. For this, CegoDistCursr desctructor method has been stabilized, so no exception is thrown. Otherwise, double memory freeing of cursor resources might occur which results in a crash - In CegoTableManager::stopTableset, relocated the setTableSetRunState method above and added a sleep of DBM_LOCKDELAY. This gives hanging db threads a chance, to terminate save - Changed CegoDatabaseManager::useObject method to take pointer to CegoTableManager as an argument instead of threadId. The tablemanager is used to support thread termination in case of lock delays - Fix in CegoTableManager::createBTree to catch exclusicve useObject timeout before committing btree. In this case, the already created btree object should be deleted. Fix added in CegoClient to active abort interrupt also during tuple fetch - Added function getcount to retrieve current counter value for a specific counter - Fix in CegoLogManager::stopLog, the log handle must NOT be deleted, otherwise, a subsequent startLog and logAction method will result in a dump. This effect has been observed while importing a single table ( via xml import ) which failed, if the table already exists. In this case, no checkpoint is written and log handle i no more valid. A subsequent modifying db request then results in a core dump.
* databases/py-minidb: Update to 2.0.6Kai Knoblich2022-02-202-5/+7
| | | | | | | | * Modernize "do-test" target while I'm here. Changelog: https://github.com/thp/minidb/compare/2.0.5...2.0.6
* databases/pecl-rrd: Update to 2.0.3Florian Smeets2022-02-193-30/+4
|
* databases/puppetdb7: Update to 7.9.2Romain Tartière2022-02-186-38/+38
| | | | | | | Release notes: https://puppet.com/docs/puppetdb/7/release_notes.html#puppetdb-792 With hat: puppet
* databases/puppetdb6: Update to 6.20.2Romain Tartière2022-02-186-34/+34
| | | | | | | Release notes: https://puppet.com/docs/puppetdb/6/release_notes.html#puppetdb-6202 With hat: puppet
* databases/emacsql: Update to latest snapshotYasuhiro Kimura2022-02-193-24/+29
| | | | | | | | | This fixes runtime error of devel/{forge,forge-devel} While here, pet portlint and portclippy Changes: https://github.com/skeeto/emacsql/compare/3.0.0...3747260 MFH: 2022Q1
* databases/pgpool-II-43: Update version 4.3.0=>4.3.1Muhammad Moinur Rahman2022-02-182-4/+4
| | | | Relnotes: https://www.pgpool.net/docs/latest/en/html/release-4-3-1.html
* databases/ora2pg: Update to 23.1Wen Heping2022-02-183-4/+5
|
* databases/py-pg8000: Update to 1.24.0Wen Heping2022-02-182-4/+4
|
* databases/adodb: set deprecation dateDima Panov2022-02-181-0/+4
| | | | | | | | Mark as DEPRECATED by 2022-03-31 While here, set IGNORE_WITH_PHP= 80 81 Sponsored by: Netzkommune GmbH
* databases/adodb5: update to 5.22.0 releaseDima Panov2022-02-183-5/+5
| | | | | Changelog: https://github.com/ADOdb/ADOdb/blob/v5.22.0/docs/changelog.md Sponsored by: Netzkommune GmbH
* databases/cassandra3: Fix dependency resolutionAngelo Polo2022-02-172-2/+3
| | | | PR: 261220
* databases/mariadb104-server: Security update to 10.4.24Bernard Spil2022-02-176-15/+21
| | | | | | PR: 261969 Security: ff5606f7-8a45-11ec-8be6-d4c9ef517024 MFH: 2022Q1
* databases/postgresql-jdbc: update to 42.3.3.Palle Girgensohn2022-02-172-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | 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 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. Security: https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-673j-qm5f-xpv8
* databases/mariadb103-server: Security update to 10.3.34Bernard Spil2022-02-176-15/+21
| | | | | | PR: 261969 Security: ff5606f7-8a45-11ec-8be6-d4c9ef517024 MFH: 2022Q1
* databases/closql: Update to 1.2.1Yasuhiro Kimura2022-02-172-5/+4
| | | | ChangeLog: https://github.com/emacscollective/closql/blob/v1.2.1/CHANGELOG
* databases/webdis: add 'restart' option to daemon(8).Jimmy Olgeni2022-02-172-1/+2
| | | | It has been reported that websockets might cause crashes occasionally.
* databases/soci: disable FIREBIRD also on riscv64Piotr Kubaj2022-02-171-0/+1
|
* databases/soci: restore FIREBIRD PLIST_SUB to fix build on non-x86Piotr Kubaj2022-02-161-5/+5
|
* databases/powa-archivist: update to 4.1.3Palle Girgensohn2022-02-153-4/+12
|
* databases/pecl-couchbase: Mark DEPRECATEDMuhammad Moinur Rahman2022-02-151-0/+4
| | | | | | | | | - Set EXPIRATION_DATE on 2022-11-28 upstream supports php 8.0 and onwards from 3.0.5. PR: 261615 Approved by: sunpoet (maintainer-timeout)
* databases/iowow: the port had been updated to version 1.4.14Alexey Dokuchaev2022-02-155-40/+5
| | | | | | | | | - Remove `post-patch' target and two patch hunks now that these issues had been fixed and integrated upstream - GC no longer useful patch (should have been removed in commit 620968a43a5f upon dropping support for EoL'ed FreeBSD 11) Reported by: portscout
* databases/mysql57-*: Update ti 5.7.37Jochen Neumeister2022-02-152-4/+4
| | | | | | Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-37.html Sponsored by: Netzkommune GmbH
* databases/mariadb105-server: Security update to 10.5.15Bernard Spil2022-02-155-9/+10
| | | | | security: ff5606f7-8a45-11ec-8be6-d4c9ef517024 MFH: 2022Q1
* databases/php-xapian: Mark DEPRECATEDMuhammad Moinur Rahman2022-02-151-0/+3
| | | | | | | | | - Set EXPIRATION_DATE on 2022-11-28 Nothin specific about php 8.x is found in upstream site. PR: 261624 Approved by: sunpoet (maintainer-timeout)
* databases/freetds: Update version 1.3.6=>1.3.9Muhammad Moinur Rahman2022-02-152-4/+4
| | | | Relnotes: https://github.com/FreeTDS/freetds/releases/tag/v1.3.9
* databases/geoserver-mysql-plugin: Update version 2.20.1=>2.20.2Muhammad Moinur Rahman2022-02-152-5/+5
|
* databases/mroonga: Update version 11.11=>12.00Muhammad Moinur Rahman2022-02-152-4/+4
| | | | Relnotes: https://mroonga.org/en/blog/2022/02/09/mroonga-12.00.html
* databases/py-alembic: Update version 1.7.5=>1.7.6Muhammad Moinur Rahman2022-02-152-4/+4
| | | | Relnotes: https://github.com/sqlalchemy/alembic/releases/tag/rel_1_7_6
* databases/py-berkeleydb: Update version 18.1.4=>18.1.5Muhammad Moinur Rahman2022-02-152-5/+8
| | | | | | | - Drop support for pyhon36 as per upstream Relnotes: https://hg.jcea.es/pybsddb/file/fd36463ece9e/docs/changelog.rst
* databases/pgbouncer: Update version 1.16.0=>1.16.1Muhammad Moinur Rahman2022-02-142-5/+6
| | | | | | | | - Add OVERRIDE for variables [1] PR: 259714 Reported by: drtr0jan@yandex.ru [1] Approved by: m.tsatsenko@gmail.com (maintainer)
* databases/sqlite3: use the right TCL even if a newer version is installedMikhail Teterin2022-02-131-0/+2
| | | | PR: 261367
* databases/postgis30: Update to 3.0.5Loïc Bartoletti2022-02-113-5/+16
| | | | | Changes: - https://git.osgeo.org/gitea/postgis/postgis/raw/tag/3.0.5/NEWS
* databases/postgresql-ogr_fdw: Update to 1.1.1Loïc Bartoletti2022-02-112-5/+4
| | | | - Support PostgreSQL 14
* databases/soci: Adopt portNeel Chauhan2022-02-111-1/+1
|
* databases/soci: Update to 4.0.3Neel Chauhan2022-02-114-68/+61
|
* databases/postgresql96-*: mark ports as expiredPalle Girgensohn2022-02-111-0/+3
| | | | | | Final release was November 11, 2021. URL: https://www.postgresql.org/support/versioning/
* databases/mysql80-server: Fix typoJochen Neumeister2022-02-101-1/+1
| | | | Sponsored by: Netzkommune GmbH
* databases/timescaledb: Update to 2.5.2Kevin Bowling2022-02-103-4/+5
| | | | Changes: https://github.com/timescale/timescaledb/releases/tag/2.5.2
* databases/postgresql??-server: Upgrade to latest versionPalle Girgensohn2022-02-1011-20/+21
| | | | | | | | | | The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 14.2, 13.6, 12.10, 11.15, and 10.20. This release fixes over 55 bugs reported over the last three months. Announcement: https://www.postgresql.org/about/news/postgresql-142-136-1210-1115-and-1020-released-2402/ Release notes: https://www.postgresql.org/docs/release/
* databases/pg_activity: Update to 2.3.0Palle Girgensohn2022-02-093-5/+5
| | | | Release notes: https://github.com/dalibo/pg_activity/releases/tag/v2.3.0
* databases/gdbm: update GNU dbm to the latest version 1.23.Alexey Dokuchaev2022-02-092-4/+4
| | | | Reported by: portscout
* databases/py-pgmigrate: Update to 1.0.7Dmitry Wagin2022-02-082-4/+4
| | | | | | | | | | 1.0.7 (2022-02-02) - Skip unnecessary schema creation on init - Add file path to statement apply error log - Add version gaps check PR: 261759
* KDE: Update KDE Gear to 21.12.2 (bug fix release)Tobias C. Berner2022-02-071-3/+3
| | | | | | | | | | | | Thursday, 3 February 2022 Over 120 individual programs plus dozens of programmer libraries and feature plugins are released simultaneously as part of KDE Gear. Today they all get new bugfix source releases with updated translations. Full changelog: https://kde.org/announcements/changelogs/gear/21.12.2/
* databases/rubygem-influxdb: update to 0.8.1Matthias Fechner2022-02-072-5/+4
| | | | | | | | | | | | | | | | | | | Changelog: https://github.com/influxdata/influxdb-ruby/blob/master/CHANGELOG.md v0.8.1, release 2021-02-17 Ensure workers can send data popped off the queue at shutdown (#239, @onlynone) Add support for special characters in password when using url keyword (#242, @swistak35) Add Ruby 3.0 support (#249, @dentarg, @paul and @track8) Support characters that need quoting for usernames and database names (#248, @estheruary) v0.8.0, released 2020-02-05 Allow dropping of specific series from specific DBs (#233, @cantino) Add support for MRI 2.7 (#235, @jeffkowalski) Raise a LineProtocolError if attempting to write empty values as field set is required. This adds descriptive feedback to the error "unable to parse '{series},{tags} ': invalid field format" (#236, @todtb) Add support for configuring HTTP Proxy (#238, @epchris)
* databases/libpg_query: update to 13-2.1.0Matthias Fechner2022-02-072-10/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changelog: https://github.com/pganalyze/libpg_query/blob/13-latest/CHANGELOG.md 13-2.1.0 2021-10-12 Normalize: add funcname error object #121 Normalize: Match GROUP BY against target list and re-use param refs #124 PL/pgSQL: Setup namespace items for parameters, support RECORD types #123 This significantly improves parsing for PL/pgSQL functions, to the extent that most functions should now parse successfully 13-2.0.7 2021-07-16 Normalize: Don't modify constants in TypeName typmods/arrayBounds fields (#118) This matches how pg_stat_statement behaves, and avoids causing parsing errors on the normalized statement Don't fail builds on systems that have strchrnul support (FreeBSD) 13-2.0.6 2021-06-29 Normalize: Don't touch "ORDER BY 1" expressions, keep original text #115 This avoids obscuring the semantic meaning of integers in the ORDER BY clause, which is to reference a particular column in the target list. 13-2.0.5 2021-06-24 Update to Postgres 13.3 patch release #114 Add optional Makefile target to build as shared library #100 Normalize: Don't touch "GROUP BY 1" type statements, keep original text #113 This avoids obscuring the semantic meaning of integers in the GROUP BY clause, which is to reference a particular column in the target list. Fingerprint: Cache list item hashes to fingerprint complex queries faster #112 This was exhibiting quite bad runtime behaviour before, causing both an explosion in memory, as well as very high CPU runtime for complex queries. The new approach ensures we don't calculate the hashes for a particular list more than once, which ensures that we roughly have quadratic runtime instead of exponential runtime. Deparser: Emit the RangeVar catalogname if present #105 Fix crash in pg_scan function when encountering backslash escapes #109 Integrate oss-fuzz fuzzer #106 13-2.0.4 2021-04-05 Deparser: Fix crash in CopyStmt with HEADER or FREEZE inside WITH parens The parse tree does not contain an explicit argument in those cases, but does when specified in the legacy mode without the wrapping WITH. With this change we only output the "1" argument when the original tree also had this, to ensure parse tree comparisons match. Note the intent here is technically the same, which is to enable these options. 13-2.0.3 2021-04-02 Normalize: Fix handling of two subsequent DefElem elements #96 We were incorrectly adding too many DefElem locations to the recorded constant values, causing a crash when more than a single DefElem is present in a utility statement. 13-2.0.2 2021-03-30 srcdata/nodetypes.json: Avoid bogus values accidentally parsed from inside comments 13-2.0.1 2021-03-30 Fix ARM builds: Avoid dependency on cpuid.h header Simplify deparser of TableLikeClause #91 Lele Gaifax Fix asprintf warnings by ensuring _GNU_SOURCE is set early enough 13-2.0.0 2021-03-18 Update to PostgreSQL 13 parser (13.2 release) Changes to JSON output format WARNING: These JSON format changes are incompatible with prior releases. New top-level result object that contains the Postgres version number the parser is based on Node type names are only output when the field is a generic field (Node*), but not when the field always has the same type. This matches how the Postgres source looks like, and ensures the JSON and (new) Protobuf format match in their structure. You can utilize the srcdata/struct_defs.json file as needed to get the necessary context on field types. Whitespace between control characters in JSON is no longer added "<" and ">" characters are escaped to avoid browser HTML injections Enum values are output with the value's name, instead of the integer value Introduce new Protobuf parse tree output format Up until now, this library relied on JSON to pass the parse result back to the caller, which has a number of downsides, most importantly that we don't have a readily available parser for JSON thats not tied to a running Postgres server. That in turn makes it hard to provide cross-language features such as deparsing directly in this library (which would require reading back a parse tree that gets passed in). Protobuf isn't perfect, but its straightforward enough to generate the schema definitions for the parse tree nodes, and output the tree using a bundled C protobuf library, which has a small enough SLOC count (~3k) to not be noticeable in the big picture. Add support for returning Postgres scanner result This allows utilizing pg_query for use cases that need the raw token information, instead of a parse tree. Due to additional modifications to the Postgres source, this also contains information about comments in the query string, and their location. Add deparsing functionality that turns parse tree back into a SQL query This is based on the deparser that was written over multiple years for the pg_query Ruby library, and is now accessible for all bindings through this new API and implementation. Fingerprinting: Introduce v3 version and 64-bit XXH3 hash See full details in the wiki page here: https://github.com/pganalyze/libpg_query/wiki/Fingerprinting#version-30-based-on-postgresql-13 Add new pg_query_split_with_scanner/pg_query_split_with_parser functions to split up multi-statement strings Naively one could assume that splitting a string by ";" is sufficient, but it becomes tricky once one takes into consideration that this character can also show up in identifier, constants or comments. We provide both a parser-based split function and a scanner-based split function. Most importantly when splitting statements in a file that may contain syntax errors that cause a parser error, but are accepted by the scanner. Otherwise the parser-based split function is recommended due to better accuracy. Add experimental Protobuf C++ outfuncs, converge JSON output to match Protobuf mapped output Extract source with USE_ASSERT_CHECKING enabled This ensures we have the necessary functions to compile an assert-enabled build if necessary. Note that this doesn't mean that asserts are enabled by default (they are not, you need to explicitly use DEBUG=1). Ensure codebase has a clean Valgrind run PL/pgSQL: Output NEW/OLD variable numbers, record dno fields Ethan Resnick Makefile: Allow passing in customized CFLAGS/PG_CONFIGURE_FLAGS/TEST_* Ethan Resnick 10-1.0.5 2021-02-17 Update to latest Postgres 10 patch release (10.16) Free Postgres top-level memory context on thread exit / with function Previously there was no way to free the top-level Postgres memory context, causing threaded programs that churn through a lot of threads to leak memory with each newly initialized thread-local top-level memory context. Instead, this uses a newly introduced cleanup method to free the memory when a pthread exits (note this causes a pthread dependency to be added to this library). In addition, primarily for memory testing purposes, add a new method "pg_query_exit" that performs the same cleanup on demand. Resolve correctness issues and possible memory leak in PL/pgSQL parser Add arch-ppc.h for PPC architectures #80 @pkubaj
* databases/percona57-server: update to 5.7.36-39 releaseDima Panov2022-02-062-4/+4
| | | | | MFH: 2022Q1 Sponsored by: Netzkommune GmbH.
generated by cgit v1.2.3 (git 2.25.1) at 2025-10-20 01:36:08 +0000