标签

 postgresql 

相关的文章:

这是一个关于 PostgreSQL 的文章合集,包括如何在 Github Actions 中添加 PostgreSQL 用于测试、理解 PostgreSQL 的 Planner、使用 pgAdmin4 连接 PostgreSQL 集群、备份配置文件、数据校验、索引扫描等内容。

Percona Database Performance Blog

Percona Database Performance Blog -

Partially Rolling Back a Transaction in MySQL or PostgreSQL

This short write-up focuses on a different transaction control behavior of databases. Though this is not unusual, I decided to write an article on rolling back transactions to a particular point. I selected this topic because I found many people are not aware of this feature in databases.DescriptionEvery ACID-compliant RDBMS follows the “All or None” […]

本文讨论了数据库事务控制行为和回滚到特定点的功能。ACID兼容的关系型数据库遵循“全部或无”的概念,出错时会回滚并不会对数据库进行更改。保存点可以将事务回滚到特定点,帮助部分回滚。

相关推荐 去reddit讨论
晓空blog

晓空blog -

在windows下PostgreSQL数据库手动安装部署

这是一份针对手动安装部署PG数据库的简易指南 正常来说直接用官方网站的安装包一路下一步就行 但是你也可能碰到安装完成,但发生了错误的情况,那么就需要手动安装处理了 https://www.enterprisedb.com/downloads/postgres-postgresql-downloads 没啥太多好说的 注意安装路径不要有中文……

这篇文章是关于手动安装和部署PG数据库的简易指南,包括下载二进制文件、初始化数据库、启动和停止数据库等步骤。同时还介绍了设置密码和安装pgAdmin的方法。文章提供了参考资料和一些碎碎念。

相关推荐 去reddit讨论
Planet PostgreSQL

Planet PostgreSQL -

Hubert 'depesz' Lubaczewski: Waiting for PostgreSQL 17 – Invent SERIALIZE option for EXPLAIN.

On 3rd of April 2024, Tom Lane committed patch: Invent SERIALIZE option for EXPLAIN.   EXPLAIN (ANALYZE, SERIALIZE) allows collection of statistics about the volume of data emitted by a query, as well as the time taken to convert the data to the on-the-wire format. Previously there was no way to investigate this without actually … Continue reading "Waiting for PostgreSQL 17 – Invent SERIALIZE option for EXPLAIN."

2024年4月3日,Tom Lane提交了一个补丁,为EXPLAIN引入了SERIALIZE选项,允许收集关于查询产生的数据量和转换数据所需时间的统计信息。这个功能特别适用于查询优化。

相关推荐 去reddit讨论
Planet PostgreSQL

Planet PostgreSQL -

Hubert 'depesz' Lubaczewski: Waiting for PostgreSQL 17 – Add new COPY option LOG_VERBOSITY.

On 1st of April 2024, Masahiko Sawada committed patch: Add new COPY option LOG_VERBOSITY.   This commit adds a new COPY option LOG_VERBOSITY, which controls the amount of messages emitted during processing. Valid values are 'default' and 'verbose'.   This is currently used in COPY FROM when ON_ERROR option is set to ignore. If 'verbose' … Continue reading "Waiting for PostgreSQL 17 – Add new COPY option LOG_VERBOSITY."

2024年4月1日,Masahiko Sawada提交了一个补丁,添加了一个新的COPY选项LOG_VERBOSITY,用于控制处理过程中发出的消息数量。有效值为'default'和'verbose'。当ON_ERROR选项设置为ignore时,在COPY FROM中使用。指定'verbose'时,会为每个丢弃的行发出一个NOTICE消息,提供额外的信息,帮助用户识别加载失败的有问题的行。

相关推荐 去reddit讨论
Planet PostgreSQL

Planet PostgreSQL -

Hubert 'depesz' Lubaczewski: Waiting for PostgreSQL 17 – Add support for MERGE … WHEN NOT MATCHED BY SOURCE.

On 30th of March 2024, Dean Rasheed committed patch: Add support for MERGE ... WHEN NOT MATCHED BY SOURCE.   This allows MERGE commands to include WHEN NOT MATCHED BY SOURCE actions, which operate on rows that exist in the target relation, but not in the data source. These actions can execute UPDATE, DELETE, or … Continue reading "Waiting for PostgreSQL 17 – Add support for MERGE … WHEN NOT MATCHED BY SOURCE."

2024年3月30日,Dean Rasheed提交了补丁,为MERGE命令添加了对WHEN NOT MATCHED BY SOURCE的支持。这个功能使得数据加载/更新过程更简单。

相关推荐 去reddit讨论
Percona Database Performance Blog

Percona Database Performance Blog -

JSON_TABLE() Will Be in PostgreSQL 17

JSON_TABLE() will be in PostgreSQL 17! It almost made it two years ago but was yanked away at the last minute. We will get it shortly when PostgreSQL 17 is officially released this year! Please see this.Why is this important?JSON has become the data interchange format of choice for most developers. JSON had a litany […]

PostgreSQL 17将引入JSON_TABLE(),使处理JSON数据更加方便。JSON_TABLE()可以将JSON数据转换为关系表,以便使用SQL命令进行处理。然而,PostgreSQL的JSON_TABLE()无法处理嵌套列。希望将来能够加入JSON模式验证等功能。

相关推荐 去reddit讨论
Planet PostgreSQL

Planet PostgreSQL -

Sai Srirampur: PeerDB raises $3.6 million seed funding to revolutionize data movement for PostgreSQL

PeerDB offers a fast and cost-effective way to move data from PostgreSQL to data warehouses, such as Snowflake, and to queues like Kafka. This enables businesses to have real-time and reliable access to data, which is of utmost importance in this AI ...

PeerDB是一种快速且具有成本效益的数据迁移平台,可将数据从PostgreSQL移动到数据仓库和队列。PeerDB的愿景是成为在Postgres上运行业务的公司的数据迁移和ETL的事实标准。PeerDB最近获得了360万美元的种子轮融资,用于扩大工程团队、推动市场营销和客户获取,并支持增长。

相关推荐 去reddit讨论
Planet PostgreSQL

Planet PostgreSQL -

Peter Eisentraut: PostgreSQL 17 commitfest conclusion

Last October, I wrote: Looking at the numbers in the PG17 cycle so far, even though they are much lower than the 2023-03 commitfest, we can expect that PG17 will have more activity in total than previous development cycles. And now it’s time to count up the score. The final per-commitfest numbers of committed patches were: PG17 2023-07 2023-09 2023-11 2024-01 2024-03 87 68 86 75 134 The 01 and 03 numbers are all-time highs for their respective months. The total numbers of committed patches registered in a commitfest for a development cycle were: PG12 319 PG13 277 PG14 360 PG15 349 PG16 433 PG17 450 So this went pretty much as I had suspected back in October. Of course, some people aren’t happy with the last minute rush. We can see how commit activity peaked in the last week (keeping in mind that 2024-04-08 was feature freeze): git log --since='2024-03-01' --until='2024-04-09' --format='%cd' --date='format:%V' master | sort | uniq -c ... 82 10 # week starting 2024-03-04 82 11 # week starting 2024-03-11 73 12 # week starting 2024-03-18 72 13 # week starting 2024-03-25 123 14 # week starting 2024-04-01 ... I look forward to checking how that works out when we look at the final release statistics such as number of release note items and number of contributors.

根据最新提交数据,PG17开发周期的活动比以往更多,最终提交的补丁数量为450,其中01和03月份创下历史新高。提交活动在最后一周达到高峰,期待发布统计数据的公布。

相关推荐 去reddit讨论
Planet PostgreSQL

Planet PostgreSQL -

David Christensen: Building PostgreSQL Extensions: Dropping Extensions and Cleanup

I recently created a Postgres extension which utilizes the pg_cron extension to schedule recurring activities using the cron.schedule(). Everything worked great. The only problem was when I dropped my extension, it left the cron job scheduled, which resulted in regular errors: 2024-04-06 16:00:00.026 EST [1548187] LOG: cron job 2 starting: SELECT bridge_stats.update_stats('55 minutes', false) 2024-04-06 16:00:00.047 EST [1580698] ERROR: schema "bridge_stats" does not exist at character 8 2024-04-06 16:00:00.047 EST [1580698] STATEMENT: SELECT bridge_stats.update_stats('55 minutes', false) If you look in the cron.job table, you can see the SQL for the cron job is still present, even though the extension/schema isn’t: select schedule, command, jobname from cron.job; schedule | command | jobname -----------+-------------------------------------------------------+---------------------------------- 0 0 * * 0 | SELECT bridge_stats.weekly_stats_update() | bridge-stats-weekly-maintenance 0 * * * * | SELECT bridge_stats.update_stats('55 minutes', false) | bridge-stats-hourly-snapshot (2 rows) This got me thinking: how can you create a Postgres extension that can clean up after itself for cases like this? How Extension Creation/Cleanup works If you’ve created or used an extension in Postgres (such as pg_partman, PostGIS, pg_kaboom, etc) you may know that every extension in PostgreSQL has a SQL file that gets run as part of the creation. This SQL file may create database objects for you, such as schemas, tables, functions, etc. When database objects are created in the context of a CREATE EXTENSION command, they have an object dependency created against the underlying pg_extension object. (These are stored in the pg_depend system catalog, if you are interested in the more fine-grained details.) When Postgres removes an extension (via the DROP EXTENSION command), it will also remove any dependent objects that were created f[...]

作者创建了一个Postgres扩展,利用pg_cron扩展来使用cron.schedule()调度重复活动。但是当删除扩展时,cron作业仍然保留,导致错误。为了解决这个问题,作者使用了EVENT TRIGGER来清理cron作业。作者尝试了不同的事件触发器类型,最终选择了ddl_command_start事件触发器类型。通过ALTER EXTENSION命令,作者成功实现了清理功能。

相关推荐 去reddit讨论
Percona Database Performance Blog

Percona Database Performance Blog -

Protect Your PostgreSQL Database with pg_tde: Safe and Secure

Tech Preview release of pg_tde now availableAs organizations collect, store, and analyze vast amounts of data, ensuring its confidentiality and integrity becomes a top priority. For PostgreSQL users, the tech preview release availability of the new encryption extension pg_tde delivers unmatched protection for vital data assets.What is pg_tde?pg_tde, developed by Percona, is an open source […]

Percona发布了pg_tde的技术预览版,这是一个为PostgreSQL提供透明数据加密功能的开源扩展。pg_tde与传统加密方法不同,它能够无缝集成到PostgreSQL中,在不中断现有工作流程的情况下对表级数据进行加密。它提供了堆表的加密、复制支持以及旋转主密钥等功能,以增强安全性。用户可以为每个数据库单独定制加密设置。Percona计划根据社区反馈对pg_tde进行改进和增强。

相关推荐 去reddit讨论

热榜 Top10

eolink
eolink
观测云
观测云
Dify.AI
Dify.AI
LigaAI
LigaAI

推荐或自荐