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 1s2Xo8-003uPX-Fu for pgsql-announce@arkaria.postgresql.org; Thu, 02 May 2024 14:53:12 +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 1s2Xo5-001S7y-Jq for pgsql-announce@arkaria.postgresql.org; Thu, 02 May 2024 14:53:10 +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 1s2Xo4-001S7n-Nf for pgsql-announce@lists.postgresql.org; Thu, 02 May 2024 14:53:09 +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 1s2Xo1-001Beo-UZ for pgsql-announce@lists.postgresql.org; Thu, 02 May 2024 14:53:09 +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=K49OhS0VccpPRUz1pPvFkXcasBltH+HQ5K0eaQIr1wg=; b=MpaKS5MZitKPVXEGtKApXiBXso IaYhTFJHFJGMOn/V9QsO9GBoJXFv8X911JfBhHoSaP1oe4C2wu1MOPK/WlZ2XYvEHTZ5M8HA3zIvH 1hcYFGBlgk74kyL21yqsWOYfdQJj7LESNodvLD2Om0i1RxDP3DzySK5bjLpf3IT56CaLYj/WolQGs /becPYFZGBSWh+Ki6ZdJhLJWwvyGreEaLwSf3bGTKWX6vTA9/FRZvn3vJNbuOZklFfqmS2B9Fclme 3lZ/cq2qvzxhkbHje1ThlEG/n+F20t9qvpkViwgXfY6Bt2xSjUJfXIWyJD5rjklfcbpFPxuVnqyy6 zVfU4IwA==; Received: from wrigleys.postgresql.org ([217.196.149.60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s2Xnz-003XtO-GO for pgsql-announce@lists.postgresql.org; Thu, 02 May 2024 14:53:04 +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 1s2Xnx-008fZo-EK for pgsql-announce@lists.postgresql.org; Thu, 02 May 2024 14:53:02 +0000 Content-Type: multipart/mixed; boundary="===============2176693528739455332==" MIME-Version: 1.0 Subject: pgEdge Distributed PostgreSQL Introduces Automatic DDL Replication and Snowflake Sequences for Postgres To: PostgreSQL Announce From: "pgEdge, Inc. via PostgreSQL Announce" Reply-To: cto@pgedge.com Date: Thu, 02 May 2024 14:52:09 +0000 Message-ID: <171466152952.700.11991336939051091631@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: proprietary X-pglister-tagsig: 28eccad1bc6a9194c7b62c841eeea45a99e2ccc598618a0b8e7f2b2169da6da3 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============2176693528739455332== Content-Type: multipart/alternative; boundary="===============1709380278963402193==" MIME-Version: 1.0 --===============1709380278963402193== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable New capabilities advance state of the art in Postgres logical replication Alexandria, VA - April 17, 2024 - pgEdge, Inc., the leading company dedicat= ed to distributed Postgres, today unveiled two major advances in logical re= plication for the widely adopted open-source PostgreSQL database. These are= automatic DDL (Data Definition Language) replication, and snowflake sequen= ces, an innovative solution to the problem of maintaining unique sequence i= dentifiers across a distributed Postgres cluster. pgEdge Distributed Postg= reSQL is the first and only fully distributed PostgreSQL database solution = that is open (source available) and completely based on the PostgreSQL data= base itself. Automatic Replication of DDL Commands. DDL is used to create and modify Postgres objects like tables, indexes, vie= ws and constraints through command statements like CREATE, ALTER, and DROP.= DML (data manipulation language) is used to perform operations on the dat= a within those database objects through command statements such as SELECT, = INSERT, UPDATE, and DELETE. =20 Traditionally, logical replication in Postgres only allowed for the replica= tion of DML statements and not DDL. Manual efforts were required on each n= ode to modify table definitions through DDL commands that had to be execute= d on every node.=20 With the introduction of automatic DDL replication on pgEdge, developers ca= n now update the database schema on a single node and have it automatically= propagated to other nodes in the cluster. This feature makes it far easier= to support distributed Postgres applications where the database schema is = frequently updated because of active development or maintenance.=20 Snowflake Sequence in Postgres Extension: Managing sequences in a distributed PostgreSQL environment can be complex, = especially in multi-master replication scenarios. A Postgres sequence prov= ides a unique integer number to use as an ID for the database table and its= records. If you insert new records it will assign the next number in the s= equence without issue. =20 In a distributed application, however, the sequence must be updated across = different regions and if each node updates the sequence independently you w= ill have conflicts that cannot be resolved. For example, if a sequence is = being used as a primary key, the next value of the sequence on a node in th= e US could be selected at the exact same time the next value of the sequenc= e is selected on a node in Australia, resulting in a primary key conflict. To address this challenge, pgEdge has integrated snowflake sequences into a= Postgres extension. A snowflake sequence allows for the utilization of a g= uaranteed unique sequence within a cluster without the need for application= code or schema modifications. By automatically installing the Snowflake ex= tension in pgEdge Platform and pgEdge Cloud databases, users can easily mai= ntain unique sequence numbers across different regions, eliminating conflic= ts and enhancing scalability.=20 An exclusive presentation and paper on the Snowflake extension will be show= cased at the Silicon Valley Postgres conference in San Jose this week. =E2=80=9CBy offering these cutting-edge capabilities built on open, standar= d-based Postgres, we demonstrate our ongoing commitment to making advanced = distributed Postgres capabilities available to the Postgres community. Our = goal is to make it easier and faster to deliver distributed Postgres applic= ations that are always on, always available and always responsive,=E2=80=9D= remarked Phillip Merrick, Co-founder and CEO of pgEdge. Availability Automatic DDL Replication and Snowflake Sequences are available now within = both pgEdge Platform (self hosted) or pgEdge Cloud (fully managed cloud ser= vice). For more information, to signup for pgEdge Cloud, or to download pgEdge Pla= tform, visit www.pgedge.com. To learn how to configure pgEdge=E2=80=99s Au= to DDL, view the documentation at https://docs.pgedge.com/platform/advanced= /autoddl. The pgEdge Snowflake extension is available on the project's Git= Hub repository at https://github.com/pgEdge/snowflake-sequences.=20 About pgEdge pgEdge, the leading company dedicated to distributed Postgres, has made its= mission to make it easy for developers to build and deploy highly distribu= ted database applications across the global network. Founded by industry ve= terans who have championed enterprise usage of the PostgreSQL database for = several decades and helped run the world=E2=80=99s largest managed database= cloud services, pgEdge is headquartered in Northern Virginia. The founders= have previously founded and/or led successful companies such as webMethods= (NASDAQ: WEBM), EnterpriseDB (acquired by Bain Capital), SparkPost (acquir= ed by MessageBird), OpenSCG (acquired by AWS) and Fugue (acquired by Snyk).= Investors in pgEdge include Sands Capital Ventures, Grotech Ventures and S= and Hill East. --===============1709380278963402193== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable pgEdge Distributed PostgreSQL Introduces Automatic DDL Replicati= on and Snowflake Sequences for Postgres
 

pgEdge Distributed PostgreSQL Introduces Automatic DDL Replication an= d Snowflake Sequences for Postgres

New capabilities advance state of the art i= n Postgres logical replication

Alexandria, VA - April 17, 2024 - pgEdge, I= nc., the leading company dedicated to distributed Postgres, today unveiled = two major advances in logical replication for the widely adopted open-sourc= e PostgreSQL database. These are automatic DDL (Data Definition Language) r= eplication, and snowflake sequences, an innovative solution to the problem = of maintaining unique sequence identifiers across a distributed Postgres cl= uster. pgEdge Distributed PostgreSQL is the first and only fully distribut= ed PostgreSQL database solution that is open (source available) and complet= ely based on the PostgreSQL database itself.

Automatic Replication of DDL Commands. DDL is used to create and modify Postgres objects like tables, indexes, vie= ws and constraints through command statements like CREATE, ALTER, and DROP.= DML (data manipulation language) is used to perform operations on the dat= a within those database objects through command statements such as SELECT, = INSERT, UPDATE, and DELETE.

Traditionally, logical replication in Postg= res only allowed for the replication of DML statements and not DDL. Manual= efforts were required on each node to modify table definitions through DDL= commands that had to be executed on every node.

With the introduction of automatic DDL repl= ication on pgEdge, developers can now update the database schema on a singl= e node and have it automatically propagated to other nodes in the cluster. = This feature makes it far easier to support distributed Postgres applicatio= ns where the database schema is frequently updated because of active develo= pment or maintenance.

Snowflake Sequence in Postgres Extension: Managing sequences in a distributed PostgreSQL environment can be complex, = especially in multi-master replication scenarios. A Postgres sequence prov= ides a unique integer number to use as an ID for the database table and its= records. If you insert new records it will assign the next number in the s= equence without issue.

In a distributed application, however, the = sequence must be updated across different regions and if each node updates = the sequence independently you will have conflicts that cannot be resolved.= For example, if a sequence is being used as a primary key, the next value= of the sequence on a node in the US could be selected at the exact same ti= me the next value of the sequence is selected on a node in Australia, resul= ting in a primary key conflict.

To address this challenge, pgEdge has integ= rated snowflake sequences into a Postgres extension. A snowflake sequence a= llows for the utilization of a guaranteed unique sequence within a cluster = without the need for application code or schema modifications. By automatic= ally installing the Snowflake extension in pgEdge Platform and pgEdge Cloud= databases, users can easily maintain unique sequence numbers across differ= ent regions, eliminating conflicts and enhancing scalability.

An exclusive presentation and paper on the = Snowflake extension will be showcased at the Silicon Valley Postgres confer= ence in San Jose this week.

=E2=80=9CBy offering these cutting-edge cap= abilities built on open, standard-based Postgres, we demonstrate our ongoin= g commitment to making advanced distributed Postgres capabilities available= to the Postgres community. Our goal is to make it easier and faster to del= iver distributed Postgres applications that are always on, always available= and always responsive,=E2=80=9D remarked Phillip Merrick, Co-founder and C= EO of pgEdge.

Availability Automatic DDL Replication and Snowflake Sequences are available now within = both pgEdge Platform (self hosted) or pgEdge Cloud (fully managed cloud ser= vice).

For more information, to signup for pgEdge = Cloud, or to download pgEdge Platform, visit www.pgedge.com. To learn how = to configure pgEdge=E2=80=99s Auto DDL, view the documentation at https://d= ocs.pgedge.com/platform/advanced/autoddl. The pgEdge Snowflake extension i= s available on the project's GitHub repository at https://github.com/pgEdge= /snowflake-sequences.

About pgEdge pgEdge, the leading company dedicated to distributed Postgres, has made its= mission to make it easy for developers to build and deploy highly distribu= ted database applications across the global network. Founded by industry ve= terans who have championed enterprise usage of the PostgreSQL database for = several decades and helped run the world=E2=80=99s largest managed database= cloud services, pgEdge is headquartered in Northern Virginia. The founders= have previously founded and/or led successful companies such as webMethods= (NASDAQ: WEBM), EnterpriseDB (acquired by Bain Capital), SparkPost (acquir= ed by MessageBird), OpenSCG (acquired by AWS) and Fugue (acquired by Snyk).= Investors in pgEdge include Sands Capital Ventures, Grotech Ventures and S= and Hill East.
This email was sent to you from pgEdge, Inc.. It was delivered on their beh= alf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to pgEdge, Inc..

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Related Proprietary. 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/.
 
--===============1709380278963402193==-- --===============2176693528739455332==--