Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rND8j-00A7w2-7b for pgsql-announce@arkaria.postgresql.org; Tue, 09 Jan 2024 14:31:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rND8h-00DNJF-LU for pgsql-announce@arkaria.postgresql.org; Tue, 09 Jan 2024 14:31:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rND4W-00D1Wl-Hr for pgsql-announce@lists.postgresql.org; Tue, 09 Jan 2024 14:27:16 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rND4N-000exA-Gt for pgsql-announce@lists.postgresql.org; Tue, 09 Jan 2024 14:27:15 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=4QccbDswqB3jggm65nhW3TfKABGP3dbhPKk7jamXzoM=; b=Id+L6ZArJL9eHnp+DvGkMoZ/pD 3ruZJ+4PjqTHQ7ZfYwSaFm9/SKbIDNpKrbuIyoa9J+49MpD9c8DON2sCZVICOyu2BQ+iTzwDwlQvL 1Q+h5z+W/1mhM8LBkQu+mc5rCnhvfsYdkP9XDCshEwRPP7n6hTO5sy0W77SwLIELwkC7Y/wjeTkj0 iroRI3WRUq18//xI0H0qRF1s01erz6KZyYwODVo+bGXaxcHnLJsWV/C+sAxxBXcL2P9DD6EFHECsF +H2c6NPn4fqRgKcStedmjGR5xglZDxIFLltXB7MsMRG1sNJUTvCQSwaFDx+WefSFQ8a2p5g4k04fr wYc4AhLA==; Received: from wrigleys.postgresql.org ([87.238.57.234]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rND4K-0023cx-Bo for pgsql-announce@lists.postgresql.org; Tue, 09 Jan 2024 14:27:06 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rND4I-0045DM-8L for pgsql-announce@lists.postgresql.org; Tue, 09 Jan 2024 14:27:02 +0000 Content-Type: multipart/mixed; boundary="===============2612163724510778434==" MIME-Version: 1.0 Subject: InfluxDB FDW 2.1.0 release To: PostgreSQL Announce From: Toshiba via PostgreSQL Announce Reply-To: p-db@swc.toshiba.co.jp Date: Tue, 09 Jan 2024 14:26:13 +0000 Message-ID: <170481037314.664.8367406966419542122@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 9a73c3e1f1de61bf30341418180e54211fb630f9f9815d6df5c86bba7e19a181 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============2612163724510778434== Content-Type: multipart/alternative; boundary="===============6772477140990494087==" MIME-Version: 1.0 --===============6772477140990494087== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable InfluxDB FDW 2.1.0 released We have just released version 2.1.0 of the Foreign Data Wrapper for InfluxD= B. This release can work with PostgreSQL 12, 13, 14, 15 and 16. This release improves following item (from 2.0.0):=20 - Support PostgreSQL 16.0=20 - Bug fix: Cannot delete when time series column defined as timestamptz type The FDW supports following features : - InfluxDB FDW supports pushed down some aggregate functions: count, stddev= , sum, max, min. - InfluxDB FDW supports INSERT, DELETE statements. - InfluxDB FDW supports bulk INSERT by using batch_size option from Postgre= SQL version 14 or later. - WHERE clauses including timestamp, interval and now() functions are pushe= d down. - LIMIT...OFFSET clauses are pushed down when there is LIMIT clause only or= both LIMIT and OFFSET. - Support schemaless mode that allows access to elements in the data file w= ithout changing the table definition by using jsonb typed column. Limitations : - UPDATE is not supported. - WITH CHECK OPTION constraints is not supported. Following limitations ori= ginate from data model and query language of InfluxDB. - Result sets have different number of rows depending on specified target l= ist. For example, SELECT field1 FROM t1 and SELECT field2 FROM t1 returns d= ifferent number of rows if the number of points with field1 and field2 are = different in InfluxDB database. - Timestamp precision may be lost because timestamp resolution of PostgreSQ= L is microseconds while that of InfluxDB is nanoseconds. - Conditions like WHERE time + interval '1 day' < now() do not work. Please= use WHERE time < now() - interval '1 day'. This is developed by Toshiba Digital Innovation Technology Center.=20 Please see the repository for details. Source repository : [https://github.com/pgspider/influxdb_fdw](https://gith= ub.com/pgspider/influxdb_fdw) --===============6772477140990494087== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable InfluxDB FDW 2.1.0 release
 

InfluxDB FDW 2.1.0 release

InfluxDB FDW 2.1.0 released

We have just released version 2.1.0 of the = Foreign Data Wrapper for InfluxDB. This release can work with PostgreSQL 12= , 13, 14, 15 and 16.

This release improves following item (from = 2.0.0):

  • Support Postgre= SQL 16.0
  • Bug fix: Cannot= delete when time series column defined as timestamptz type

The FDW supports following features :

  • InfluxDB FDW su= pports pushed down some aggregate functions: count, stddev, sum, max, min.<= /li>
  • InfluxDB FDW su= pports INSERT, DELETE statements.
  • InfluxDB FDW su= pports bulk INSERT by using batch_size option from PostgreSQL version 14 or= later.
  • WHERE clauses i= ncluding timestamp, interval and now() functions are pushed down.
  • LIMIT...OFFSET = clauses are pushed down when there is LIMIT clause only or both LIMIT and O= FFSET.
  • Support schemal= ess mode that allows access to elements in the data file without changing t= he table definition by using jsonb typed column.

Limitations :

  • UPDATE is not s= upported.
  • WITH CHECK OPTI= ON constraints is not supported. Following limitations originate from data = model and query language of InfluxDB.
  • Result sets hav= e different number of rows depending on specified target list. For example,= SELECT field1 FROM t1 and SELECT field2 FROM t1 returns different number o= f rows if the number of points with field1 and field2 are different in Infl= uxDB database.
  • Timestamp preci= sion may be lost because timestamp resolution of PostgreSQL is microseconds= while that of InfluxDB is nanoseconds.
  • Conditions like= WHERE time + interval '1 day' < now() do not work. Please use WHERE tim= e < now() - interval '1 day'.

This is developed by Toshiba Digital Innova= tion Technology Center.=20 Please see the repository for details. Source repository : https://github.com/pgspi= der/influxdb_fdw
This email was sent to you from Toshiba. It was delivered on their behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to Toshiba.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Related Open Source. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============6772477140990494087==-- --===============2612163724510778434==--