<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>C on ads' corner</title><link>https://andreas.scherbaum.la/tags/c/</link><description>Recent content in C on ads' corner</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 04 Dec 2025 00:00:00 +0200</lastBuildDate><atom:link href="https://andreas.scherbaum.la/tags/c/index.xml" rel="self" type="application/rss+xml"/><item><title>The 1600 columns limit in PostgreSQL - how many columns fit into a table</title><link>https://andreas.scherbaum.la/post/2025-12-04_the-1600-columns-limit-in-postgresql-how-many-columns-fit-into-a-table/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2025-12-04_the-1600-columns-limit-in-postgresql-how-many-columns-fit-into-a-table/</guid><description>&lt;p&gt;A recent blog posting by &lt;a href="https://postgresql.life/post/frederic_delacourt/"&gt;Frédéric Delacourt&lt;/a&gt; (&lt;a href="https://www.data-bene.io/en/blog/did-you-know-tables-in-postgresql-are-limited-to-1600-columns/"&gt;Did you know? Tables in PostgreSQL are limited to 1,600 columns&lt;/a&gt;) reminded me once again that in the analytics world customers sometimes ask for more than 1600 columns.&lt;/p&gt;&#10;&lt;p&gt;Quick recap: in &lt;a href="https://en.wikipedia.org/wiki/Online_transaction_processing"&gt;OLTP&lt;/a&gt;, the aim is (usually) to use the &lt;a href="https://en.wikipedia.org/wiki/Third_normal_form"&gt;3rd normal form&lt;/a&gt;. In &lt;a href="https://en.wikipedia.org/wiki/Online_analytical_processing"&gt;OLAP&lt;/a&gt;, tables are often only vaguely normalized, and wide or very wide fact tables in &lt;a href="https://en.wikipedia.org/wiki/Second_normal_form"&gt;2nd normal form&lt;/a&gt; are quite common. But are 1600 columns a bad idea? Yes. Do some applications generate such wide tables? Also yes. I&amp;rsquo;ve seen my fair share of customer requests and support tickets asking if the 1600 columns limit can be raised or even lifted.&lt;/p&gt;</description></item><item><title>PostgreSQL Hacking Workshop - August 2024</title><link>https://andreas.scherbaum.la/post/2024-08-29_postgresql-hacking-workshop-august-2024/</link><pubDate>Thu, 29 Aug 2024 00:00:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2024-08-29_postgresql-hacking-workshop-august-2024/</guid><description>&lt;p&gt;On August 8th and August 15th, the first two “&lt;a href="https://rhaas.blogspot.com/2024/07/postgresql-hacking-workshop-august-2024.html"&gt;PostgreSQL Hacking Workshops&lt;/a&gt;” took place. Robert Haas previously asked on Discord for topics, and the highest vote was for “PostgreSQL Optimizer Methodology”. The invited attendees are expected to watch the video before, and bring questions to the workshop.&lt;/p&gt;</description></item><item><title>PGSQL Phriday #007 – Triggers for tracking changes in a table</title><link>https://andreas.scherbaum.la/post/2023-04-10_pgsql-phriday-007-triggers-for-tracking-changes-in-a-table/</link><pubDate>Mon, 10 Apr 2023 17:58:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2023-04-10_pgsql-phriday-007-triggers-for-tracking-changes-in-a-table/</guid><description>&lt;p&gt;This month&amp;rsquo;s &lt;a href="https://www.pgsqlphriday.com/"&gt;#PGSQLPhriday&lt;/a&gt; is hosted by Lætita Avrot, and she asks about &lt;a href="https://mydbanotebook.org/post/triggers/"&gt;triggers&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;History time. Shortly after I started using &lt;em&gt;PostgreSQL&lt;/em&gt;, I had a need to track changes in tables. Back then - this was the early version 7.x days - there was no such option available. I set out to write a tool for it. The logical choice to do that was to pick triggers to implement this. Today the world is different, &lt;em&gt;PostgreSQL&lt;/em&gt; gained replication, and along with this, one can hook tools into the replication and stream all the changes. Back then there was no replication.&lt;/p&gt;</description></item><item><title>GSoC 2021 completed</title><link>https://andreas.scherbaum.la/post/2021-09-02_gsoc-2021-completed/</link><pubDate>Thu, 02 Sep 2021 00:06:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2021-09-02_gsoc-2021-completed/</guid><description>&lt;p&gt;The &lt;a href="https://summerofcode.withgoogle.com/"&gt;Google Summer of Code 2021&lt;/a&gt; (&lt;em&gt;GSoC&lt;/em&gt;) for the &lt;a href="https://www.postgresql.org/"&gt;PostgreSQL Project&lt;/a&gt; is wrapped up. The timeline this year was shortened to half, compared to previous years. That’s good, because smaller projects can be worked on, and students have a chance to cope with a changing environment at home and university. On the other hand, the shorter time doesn’t allow diving into more complex projects. Nevertheless, with the help of all mentors, six students successfully concluded their projects.&lt;/p&gt;</description></item><item><title>PostgreSQL Project @ GSoC 2021</title><link>https://andreas.scherbaum.la/post/2021-05-20_postgresql-project-gsoc-2021/</link><pubDate>Thu, 20 May 2021 15:25:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2021-05-20_postgresql-project-gsoc-2021/</guid><description>&lt;p&gt;Wow! The &lt;a href="https://www.postgresql.org/"&gt;PostgreSQL Project&lt;/a&gt; got all 7 proposals accepted into &lt;a href="https://summerofcode.withgoogle.com/"&gt;Google Summer of Code 2021&lt;/a&gt; (&lt;em&gt;GSoC&lt;/em&gt;)!&lt;/p&gt;&#10;&lt;p&gt;This year &lt;em&gt;Google&lt;/em&gt; changed the &lt;a href="https://summerofcode.withgoogle.com/how-it-works/"&gt;participation terms&lt;/a&gt; a bit, and cut the time for the students in half. This is supposed to help students who can’t work full-time from home, especially in light of the global pandemic situation. It also means smaller projects, which are easier to handle even for students new to the project.&lt;/p&gt;</description></item></channel></rss>