ACUVA

Your Accurate Search for New Technology

Amazon Aurora PostgreSQL now supports pgvector v0.5.0 with HNSW indexing

By

Amazon Aurora PostgreSQL-Compatible Edition now supports v0.5.0 of the pgvector extension to store embeddings from machine learning (ML) models in your database and to perform efficient similarity searches. This version includes Hierarchical Navigable Small World (HNSW) indexing support, parallelization of ivfflat index builds, and improves performance of its distance functions.

Amazon Aurora supports PostgreSQL 15.4, 14.9, 13.12, 12.16, and 11.21 versions

By

Following the announcement of updates to the PostgreSQL database by the open source community, we have updated Amazon Aurora PostgreSQL-Compatible Edition to support PostgreSQL 15.4, 14.9, 13.12, 12.16, and 11.21. These releases contains product improvements and bug fixes made by the PostgreSQL community, along with Aurora-specific improvements. This release also contains new features and improvements such as Babelfish for Aurora PostgreSQL version 3.3 . Refer to the Aurora version policy to help you to decide how often to upgrade and how to plan your upgrade process. As a reminder, if you are running any version of Amazon Aurora PostgreSQL 11,  you must upgrade to a newer major version by February 29, 2024. 

AWS CodePipeline supports parameterized pipelines

By

Today, AWS CodePipeline announces the general availability of parameterized pipelines, a new feature that enables customers to dynamically pass input parameters to a pipeline execution. For a pipeline to accept input parameters, customers have to declare the variables and use them in action configurations. When releasing a change through the console, customers can set values for variables to use in the pipeline execution. These input variables can be used in configuration of all action types except Source action types. Customers can also set the values for the input parameters when starting a pipeline through API, CLI, SDK and CDK.

AWS CodePipeline supports triggering on git tags

By

Today, AWS CodePipeline announces support for staring a pipeline execution on git tags pushed to repositories in GitHub, GitHub Enterprise Server, GitLab Cloud and Bitbucket Cloud using CodeStarSourceConnection source actions. Customers can now add a “triggers” section in their pipeline definition that has a filter for git tags using include and exclude patterns. When a git tag applied to a commit in the source repository matches the trigger filter, CodePipeline starts a pipeline execution. The CodeStarSourceConnection action clones the commit associated with the git tag. Customers can see the git tag that started the pipeline execution in the console as output variable of the corresponding source action. Customers can use the triggers section using API/CLI/SDK and CDK.

Scroll Up