Postgres Insider Terminology
crunchydata.com
Postgres Insider Terminology
1–10 of 36 posts
Re: Postgres Insider Terminology
#2That cookie banner takes you to the main page when you try to close it on mobile.
Super annoying.
Re: Postgres Insider Terminology
#3Array and relation are definitely not insider terms.
Re: Postgres Insider Terminology
#4When studying the internals of Postgres years ago, I learned that pages could greatly affect the disk space required to hold a table. If the page size was 8192 bytes (the default) and if the schema defined each row as holding 4097 bytes, then two rows would not fit within a single page. This would cause every row to be within its own page and would waste almost half of the space.
Anyone know if this is still true?
Re: Postgres Insider Terminology
#5When studying the internals of Postgres years ago, I learned that pages could greatly affect the disk space required to hold a table. If the page size was 8192 bytes (the default) and if the schema defined each row as holding 4097 bytes, then two rows would not fit within a single page. This would cause every row to be within its own page and would waste almost half of the space. Anyone know if this is still true?
Afaik, this is still true in most cases.*
this is true for almost every database.
* Except, maybe, toast, hot or compressed..
Re: Postgres Insider Terminology
#6When studying the internals of Postgres years ago, I learned that pages could greatly affect the disk space required to hold a table. If the page size was 8192 bytes (the default) and if the schema defined each row as holding 4097 bytes, then two rows would not fit within a single page. This would cause every row to be within its own page and would waste almost half of the space. Anyone know if this is still true?
Afaik, this is still true in most cases.* this is true for almost every database. * Except, maybe, toast, hot or compressed..
> this is true for almost every database.
...that uses fixed sized pages.
Re: Postgres Insider Terminology
#7I was confused by the author's definition of a relation. They said that a single tuple is an "unary relation". They probably meant a single-tuple (1-tuple).
Removing the hyphen changes the meaning. https://en.wikipedia.org/wiki/Finitary_relation
Re: Postgres Insider Terminology
#8Re: Postgres Insider Terminology
#9Re: Postgres Insider Terminology
#10Earlier quoted context omitted.
so true for almost every sql database? or not?
MyRocks is MySQL backed by an LSM tree, and so it doesn't have fixed sized pages.
so a mysql storage engine that uses the rocksdb key/value store?
sounds like could be one of those rule-proving exceptions, even if it is a big facebook project