This was originally written in September 2018, but never published (for unknown reasons). I found it in the drafts section of the website today. In this post, you will see me change approach and not use a secondary table in one instance, but use multiple secondary tables in another. In one case, you will also […]
Using triggers to update a table with calculated values Read More »
I’m so very happy about recent changes to the website. It’s been a great day. I was volunteering at a flu shot clinic. A new coffee shop has opened up, and I was there before the clinic. After the clinic, it was walking the dog, then some serious changes to the the PostgreSQL queries which
Great changes to the websites Read More »
The front page of FreshPorts is about to change, slightly. At present, the front page contains only the the commits to the main branch of the FreeBSD. More precisely, it does not include: Commits to Mk/ or other similar non-port entities within the ports tree Commits to the quarterly branch (whatever the latest quarter is;
Displaying all ports tree commits on the front page Read More »
The SQL injection issues, at least all that I could find, are fixed. The first alert was on March 18th. That went out via: Twitter account status page a notice on the top of each page of the website See also FreshSource code fixes. Short version everything we know about is fixed we saw no
SQL injection issues fixed Read More »
In this post, I’ll talk about how someone was able to use SQL injection to spin up the database server to 100% utilization. I found the queries in the logs, duplicated the situation on dev, patched the code, and updated the website. See also SQL inejection issues fixed. In this post: FreeBSD 13.1 PostgreSQL server
FreshSource code fixes Read More »
Yesterday, an incident with a commit wound up taking up a lot of time to process on FreshPorts. The purpose of this post includes: document how the commit was handled on different nodes document the fixes for some nodes investigate how the code can be improved to detect such situations and abort See also How
When a commit goes wrong Read More »
The packages_raw gets reloaded. A lot. Every time a new set of packages is available from the FreeBSD packages table, data gets deleted and reloaded. So I manually vacuum the table. Well, it’s automated, as part of the code, but it doesn’t wait for the daily scripts. I was seeing these errors on server r720-02:
Fixing permissions on the packages_raw table Read More »
When setting up a new FreshPorts ingress node, the repositories must be configured with tags so FreshPorts knows the last commit it has processed. This is the starting point each time FreshPorts goes to search for new commits. This post about Processing commits on branches with git might help with background. Those tags must be
Configuring the repo for a new ingress node Read More »
The commits.php page has a long history dating back to 2006 in GitHub and before that in another repo. Soon, it is going away. The justification is in issue 337: it’s not used much, and it’s not doing as it should (loading the last 100 commits). In the early days, the front page showed only
/commits.php is going away Read More »
This post documents how I’m changing the search methods for pkg-message. It uses full-text search, but instead of using a special column, I’m going to use an index. I will elaborate. When searching pkg-message was added to the website, a different approach was taken than in the past. In Converting a column-based expression to a
Moving from storing the tsvector values to a tsvector index Read More »