Skip to content
Written with Claude
IMPORTANT

As you may notice, this page and pretty much the entire website were obviously created with the help of AI. I wonder how you could tell? Was it a big "Written With Claude" badge on every page? I moved it to the top now (with the help of AI of course) to make it even more obvious. There are a few blogposts that were written by me manually, the old-fashioned way, I hope there will be more in the future, and those have a similar "Human Written" badge. This project (not the website), on the other hand, is a very, very different story. It took me more than two years of painstaking and unpaid work in my own free time. A story that, hopefully, I will tell someday. But meanwhile, what would you like me to do? To create a complex documentation website with a bunch of highly technical articles with the help of AI and fake it, to give you an illusion that I also did that manually? Like the half of itnernet is doing at this point? How does that makes any sense? Is that even fair to you? Or maybe to create this website manually, the old-fashioned way, just for you? While working a paid job for a salary, most of you wouldn't even get up in the morning. Would you like me to sing you a song while we're at it? For your personal entertainment? Seriously, get a grip. Do you find this information less valuable because of the way this website was created? I give my best to fix it to keep the information as accurate as possible, and I think it is very accurate at this point. If you find some mistakes, inaccurancies or problems, there is a comment section at the bottom of every page, which I also made with the help of the AI. And I woould very much appreciate if you leave your feedback there. Look, I'm just a guy who likes SQL, that's all. If you don't approve of how this website was constructed and the use of AI tools, I suggest closing this page and never wever coming back. And good riddance. And I would ban your access if I could know how. Thank you for your attention to this matter.

Changelog v3.4.7 (2025-01-21)

Version 3.4.7 (2025-01-21)

Full Changelog

Type Category Lookup Optimization

Introduced TypeCategory flags enum and pre-computed lookup table for O(1) type dispatch, replacing sequential if-chain conditionals in hot paths.

New Files:

  • TypeCategory.cs - Flags enum (Numeric, Boolean, Json, Text, DateTime, Date, NeedsEscape, CastToText, Binary, Time) and TypeCategoryLookup static class with 128-element array for instant type classification
  • ParameterParsers.cs - Delegate array for O(1) parameter parser lookup by NpgsqlDbType

Changes:

  • TypeDescriptor now has a Category property computed once at construction via lookup table
  • Boolean properties (IsNumeric, IsJson, IsText, etc.) are now computed from Category using bitwise operations
  • NpgsqlRestEndpoint.cs and PgConverters.cs use bitwise category checks for type dispatch

Benchmark Results:

OperationBeforeAfterImprovement
Type category lookup (18 types)22.6 ns6.6 ns70% faster
TypeDescriptor construction232.8 ns164.2 ns29% faster
Parser delegate lookup7.6 ns5.9 ns23% faster
Combined type check (bitwise vs properties)7.97 ns4.94 ns38% faster
Serialization type check (1000 rows)5,572 ns4,060 ns27% faster

Note: While micro-benchmarks show significant improvements, real-world endpoint throughput gains are modest (1-5%) since type dispatch is a small fraction of total request time compared to database I/O and serialization.

Additional Allocation Optimizations

Parameter Logging String Allocations

Replaced string.Concat() with paramIndex.ToString() in 8 logging paths with direct StringBuilder.Append(int) calls, eliminating intermediate string allocations for each logged parameter.

Before:

csharp
csharp
cmdLog!.AppendLine(string.Concat("-- $", paramIndex.ToString(), " ", ...));

After:

csharp
csharp
cmdLog!.Append("-- $").Append(paramIndex).Append(' ').Append(...).AppendLine(p);

Cache Key String Reuse

Cache key string (cacheKeys.ToString()) was being called 3-6 times per cached request. Now computed once and reused:

csharp
csharp
string? cacheKeyString = cacheKeys?.ToString();
// Reused in all cache Get/AddOrUpdate calls

Impact: Eliminates 8+ string allocations per parameter-heavy request (logging) and 2-5 allocations per cached request (cache keys).


Comments