Databases should contain their own Metadata – Use SQL Everywhere
floedb.ai
floedb.ai
But then, they're also doing JOINs with the USING clause, which seems like one of those things that everybody tries... until they hit one of the several reasons not to use them, and then they go back to the ON clause which is explicit and concrete and works great in all cases.
Personally, I'd like to hear more about the claims made about Snowflake IDs.
I'm ashamed to say that despite using SQL from the late 1980s, and as someone that likes reading manuals and text books, I'd never come across USING. Probably a bit late for me now to use it (or not) :-(
Not all databases support it. But once you start using it (pun) - a lot of naming conventions snap into place.
It has some funky semantics you should be aware of. Consider this:
CREATE TABLE foo (x INT);
CREATE TABLE bar (x INT);
SELECT \* FROM foo JOIN bar USING (x);
First, you need to be aware of the implicit disambiguration. When you join with USING, you are introducing a hidden column that represents both sides. This is typically what you want - but it can bite you.
Consider this PostgreSQL example:
CREATE TABLE foo (x INT);
INSERT INTO foo VALUeS (1);
CREATE TABLE bar (x FLOAT);
INSERT INTO bar VALUES (1);
SELECT pg_typeof(x) FROM foo JOIN bar USING (x);
Merge Join (cost=338.29..931.54 rows=28815 width=4)
Merge Cond: (bar.x = ((foo.x)::double precision))
It also means that this actually works:
CREATE TABLE foo (x INT);
INSERT INTO foo VALUeS (1);
CREATE TABLE bar (x INT);
INSERT INTO bar VALUES (1);
CREATE TABLE baz (x INT);
INSERT INTO baz VALUES (1);
SELECT \*
FROM foo
JOIN bar USING (x)
JOIN baz USING (x);
If you are both the data modeller and the query writer - I have not been able to come up with a reason for not USING.
The short story:
They are bit like UUID in that you can generate them across a system in a distributed way without coordination. Unlike UUID they are only 64-bit.
The first bits of the snowflake ID are structured in such a way that the values end up roughly sequentially ordered on disk. That makes them great for large tables where you need to locate specific values (such a those that store query information).
> Which tables have a column with the name country where that column has more than two different values
But on their product page, the definition of floesql left me puzzled
> It uses intelligent caching and LLVM-based vectorized execution to deliver the query execution speed your business users expect.
> With its powerful query planner, FloeSQL executes queries with lots of joins and complicated SQL syntax without breaking your budget.
The Floe engine is a full database on top of Iceberg and Delta storage. The system views are just the tip of the iceberg. We will be blogging more about what we are building.
Things are great in your DB... until they aren't. The post is about making observability a first-class citizen. Plans and query execution statistics, for example, queryable using a uniform interface (SQL) without the need to install DB extensions.
By making the entire architecture of the database visible via system objects - you allow the user to form a mental model of how the database itself works. Instead of it being just a magic box that runs queries - it becomes a fully instrumented data model of itself.
Now, you could say: "The database should just work" and perhaps claim that it is design error when it doesn't. Why do I need instrumentation at this level?
To that I can say: Every database ever made makes query planning mistakes or has places where it misbehaves. That's just the way this field works - because data is fiendishly complicated - particularly at high concurrency of when there is a lot of it. The solution isn't (just) to keep improving and fixing edge cases - it is to make those edge cases easy to detect for all users.
It's great to have that observability functionality, but I don't really understand the purpose of writing a new DBMS from scratch to add this though. Why not get something merged into Postgres core?
[1] https://dev.mysql.com/doc/refman/8.4/en/performance-schema.h...
I don't think so...
And yes, its conceptually similar to MySQL and also conceptually similar to SQL Servers implementation from 1997. That's by the design. Obviously, we are not writing a new DBMS from scratch just to add system objects.
Have a look at some of the other blogs on that site to see what we are up to. Basically, we want to give you an experience that resemblers that instrumentation you got used to from the on-premise databases, but one that can run on top of Iceberg in the cloud.
Part of my confusion was that this blog post makes no mention whatsoever of any of those things!
It gave me the (incorrect) impression that this observability functionality was the purpose of the product. And it is worded in a way which makes no mention of prior art in built-in DBMS observability.
Looking at the other threads here, I don't think I'm the only one who was confused about that. A couple intro paragraphs to the product might help a lot.
Thanks for letting me know - you can stare yourself blind on that stuff
Original author here (no, I am not an LLM).
First, a clarifying point on INFORMATION_SCHEMA. In the post I make it clear that this interface is supported by pretty much every database since the 1980s. Most tools would not exist without them. When you write an article like this - you are trying to hit a broad audience and not everyone knows that there are standards for this.
But, our design goes further and treats all metadata as data. It's joinable, persisted and acts, in every way, like all other data. Of course, some data we cannot allow you to delete - such as that in `sys.session_log` - because it is also an audit trail.
Consider, by contrast, PostgreSQL's `pg_stat_statements`. This is an aggregated, in memory, summary of recent statements. You can get a the high level view, but you cannot get every statement run and how that particular statement deviated from statements like it. You also cannot get the query plan for a statement that ran last week.
To address the obvious question: "Isn't that very expensive to store?"
Not really. Consider a pretty aggressive analytical system (not OLTP) - you get perhaps 1000 queries/sec. The query text is normalised and so is the plan - so the actual query data (runtimes, usernames, skewness, stats about various operators) is in the order of few hundred bytes. Even on a heavily used system, we are talking some double digit GB every day for a very busy system - on cheap Object Storage. Your company web servers store orders of magnitude more data than that in their logs.
With a bit of data rotation - you can keep the aggregates sizes over time manageable.
What stats do we store about queries?
- Rows in each node (count, not the actual row data as that would be a PII problem) - Various runtimes - Metadata about who, when and where (ex: cluster location)
Again, these are tiny amounts of data in the grand schema of things. But somehow our industry accepts that our web servers store all that - but our open source databases don't (this level of detail is not controversial in the old school databases by the way).
Of course, we can go further than just measuring the query plan.
Performance Profiling of workers is a a concept you can talk about - so it is also metadata. Let us say you want to really understand what is going on inside a node in a cluster.
You can do this:
```sql SELECT stack_frame, samples FROM sys.node_trace WHERE node_id = 42 ```
Which returns a 10 second sample (via `perf`) of the process running on one of the cluster node.
(Obviously, that data is emphemeral - we are good at making things fast but we can't make tracing completely free)
Happy to answer all questions