# dump Published articles for dump. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Investigating a Suspected Memory Leak in JetBrains Jewel with JVM Heap Analysis DevFeed: [Investigating a Suspected Memory Leak in JetBrains Jewel with JVM Heap Analysis]() Original publisher: [Read original article]() Published: 2026-07-28T18:00:00Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Memory Leaks](), [Compose](), [compose-multiplatform](), [jetbrains](), [ide]() Tags: [compose](), [compose-multiplatform](), [dump](), [eclipse](), [heap](), [jetbrains](), [kotlin-multiplatform](), [memory-leak]() ### AI overview The article investigates a suspected memory leak in the JetBrains Jewel project, a Compose Multiplatform library targeting desktop applications. It explains using JVM-specific tools, including heap dumps and Eclipse Memory Analyzer Tool, to examine retained heap and identify possible memory-retention issues. ### Source excerpt A kinda-brief tale about a memory leak, a heap dump, and a one-line fix. ## Gookies : A Chrome cookie dumper DevFeed: [Gookies : A Chrome cookie dumper]() Original publisher: [Read original article]() Author: CCob Published: 2020-02-21T17:56:12Z Content type: article Language: en Sources: [Ethical Chaos]() Topics: [Chrome](), [Encryption](), [Go Language](), [JSON](), [cURL](), [Windows](), [Command-line interface](), [GitHub]() Tags: [browsers](), [chrome](), [command-line](), [cookies](), [curl](), [decrypt](), [dump](), [encryption](), [github](), [go](), [golang](), [json](), [windows]() ### AI overview The article introduces Gookies, a Go-based tool that decrypts and dumps Chrome cookies. It supports multiple Chrome profiles, domain filtering, JSON output for cookie-manager import, and canonicalized cookie headers for command-line tools such as curl. The article states that Chrome 80 and later use a different cookie encryption scheme from version 79 and earlier, and that the tool currently supports Windows. ### Source excerpt A Chrome cookie decryptor and dumping tool The post Gookies : A Chrome cookie dumper appeared first on Ethical Chaos. ## NodeJS 内存泄漏检测与定位 DevFeed: [NodeJS 内存泄漏检测与定位]() Original publisher: [Read original article]() Author: Joway Published: 2019-11-10T00:00:00Z Content type: tutorial Language: zh Sources: [Random Thoughts]() Topics: [Node.js](), [developer tooling](), [Chrome](), [bug]() Tags: [bug](), [chrome](), [comparison](), [devtools](), [dump](), [nodejs](), [object](), [snapshot](), [string](), [tech]() ### AI overview This Chinese tutorial documents diagnosing and locating a Node.js memory leak using heapdump files and Chrome DevTools. It explains how to obtain heap snapshots, compare snapshots over time, and inspect object references and retained size while noting that increased memory or retained size alone does not conclusively prove a leak. ### Source excerpt 最近解决了一个 Node.JS 应用内存泄漏 Bug，顺便学会了用 Chrome DevTools 去看 heapdump 文件。这里做一些简单的记录。 如何「优雅地」获得 heapdump 文件 由于我们所有应用都是以容器部署的，所以要去获得某个容器内的文件，并拷贝到本地难度还是比较大，也非常麻烦。考虑到调试时或许会需要下载非常多次的 snapshot 文件，建议可以包下 heapdump 库，做成一个接口，把文件 dump 之后再传输给客户端，这样一劳永逸。 ## How We Solved a Storage Problem in PostgreSQL Without Adding a Single Byte of Storage DevFeed: [How We Solved a Storage Problem in PostgreSQL Without Adding a Single Byte of Storage]() Original publisher: [Read original article]() Author: Haki Benita Published: 2018-12-21T22:00:00Z Content type: tutorial Language: en Sources: [Haki Benita]() Topics: [PostgreSQL](), [etl](), [Database](), [hash](), [Sorting]() Tags: [articles](), [dataset](), [disk-space](), [dump](), [etl](), [hash](), [performance](), [postgresql](), [query](), [sorting](), [sql](), [storage]() ### AI overview This article explains how an ETL task for removing duplicate binary records in PostgreSQL caused increasing temporary disk-space usage. The author reduced the sorting key by hashing the binary value with md5, lowering additional disk usage from about 30 MB to about 4 MB without adding storage. ### Source excerpt A while back we started getting alerts in the middle of the night on low disk space. A quick investigation led us to one of our ETL tasks. Every night the task was fired to eliminate duplicate dumps, and free up some space. This is a short story about how we found our silver bullet and solved the issue without adding a single byte of storage. ## Postgres backups: Logical vs. Physical an overview DevFeed: [Postgres backups: Logical vs. Physical an overview]() Original publisher: [Read original article]() Author: Map Published: 2017-09-03T20:55:56Z Content type: tutorial Language: en Sources: [Craig Kerstiens]() Topics: [backups](), [Database](), [Databases](), [data]() Tags: [backing-up](), [backup](), [backups](), [checksums](), [dump](), [environments](), [logical](), [overview](), [pg-dump](), [portable](), [postgres](), [postgresql](), [production](), [sql](), [wal]() ### AI overview This article explains PostgreSQL's two backup types: logical backups, which are portable and can target selected tables but add database load, and physical backups, which consist of the database's bytes on disk. It also discusses checksums, corruption detection, and the role of the write-ahead log. ### Source excerpt It's not a very disputed topic that you should backup your database, and further test your backups. What is a little less discussed, at least for Postgres, is the types of backups that exist. Within Postgres there are two forms of backups and understanding them is a useful foundation for anyone working with Postgres. The two backup types are Physical: which consist of the actual bytes on disk, Logical: which is a more portable format. Let's dig into each a bit more so you can better assess which makes sense for you. Logical backups Logical backups are the most well known type within Postgres. This is what you get when you run pg_dump against a database. There are a number of different formats you can get from logical backups and Postgres does a good job of making it easy to compress and configure this backup how you see fit. When a logical backup is run against a database it is not throttled, this introduces a noticable load on your database. As it's reading the data from disk and generating (in layman terms) a bunch of SQL INSERT statements, it has to actually see the data. It's of note that older Postgres databases (read: prior to 9.3) there were no checksums against your database. Checksums are just one tool for you to help check against data corruption. Because a logical dump has to actually read and generate the data to insert it will discover any corruption that exists for you. This portable format is also very useful to pull down copies from production to different environments. I.e. if you need a copy of production data down on your local laptop pg_dump is the way to do it. Logical backups are also database specific, but then allow you to dump only certain tables. All in all logical backups bring some good features, but come at two cost: Load on your system The backup contains data as of the time when it ran Physical backups Physical backups are another option when it comes to backing up your database. As we mentioned earlier it is the physical bytes on disk ## Dump a PostgreSQL table as insert statements DevFeed: [Dump a PostgreSQL table as insert statements]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2015-02-19T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [PostgreSQL](), [Databases](), [SQL](), [Command-line interface]() Tags: [command-line](), [dump](), [insert](), [postgresql](), [sql]() ### AI overview A quick tutorial on dumping a single PostgreSQL table as SQL INSERT statements so its data can be shared for frontend testing without dumping the entire database. ### Source excerpt FYI: Like the previous post, this is a really quick tip. ## Resetting sequences. All of them, please! DevFeed: [Resetting sequences. All of them, please!]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2010-02-16T15:23:00Z Content type: tutorial Language: en Sources: [Dimitri Fontaine]() Topics: [Sequences](), [Scripting](), [SQL](), [Databases]() Tags: [dump](), [irc](), [production](), [script](), [scripting](), [sequences](), [sql](), [support]() ### AI overview A blog article explains how to restore sequence values after a production dump has been filtered. It describes querying the database catalog for all sequences and generating commands to reset them, with execution in an explicit transaction block. ### Source excerpt So, after restoring a production dump with intermediate filtering, none of our sequences were set to the right value. I could have tried to review the process of filtering the dump here, but it's a one-shot action and you know what that sometimes mean. With some pressure you don't script enough of it and you just crawl more and more. Still, I think how I solved it is worthy of a blog entry. Not that it's about a super unusual clever trick, quite the contrary, because questions involving this trick are often encountered on the support IRC.