The way that the "Postgres", "libpq" terminology is used in the article ("libpq, the API backend for Postgres") leaves me more confused than I was before. I would understand "libpq" as the client-side library implementing the PostgreSQL wire protocol, and "Postgres" as the PostgreSQL server implementation, but I think in this article "Postgres" seems to refer to the psql CLI implementation?
> I’d like to dig more into how a C FILE reference is created on the server to utilize the above code. I plan to also do more more digging on the libpq side of this operation, including how the data is written to the WAL and processed
I don't think libpq has anything to do with WAL processing, and I would likely guess that the PostgreSQL server implementation actually uses mmap?
> I’d like to dig more into how a C FILE reference is created on the server to utilize the above code. I plan to also do more more digging on the libpq side of this operation, including how the data is written to the WAL and processed
I don't think libpq has anything to do with WAL processing, and I would likely guess that the PostgreSQL server implementation actually uses mmap?