Infrastructure at your Service
Currently a lot of stuff is being committed for PostgreSQL and what we will look at in this post is a feature, I am sure, a lot of PostgreSQL users have been waiting for for a long time: Finally there is a native way to validate your base backups: pg_validatebackup. This is a new binary that can be used to validate base backups against a backup manifest, that is written automatically when you do backup…
In the last post we had a look at DB Parameter Groups when it comes to AWS RDS for PostgreSQL. This is one of the first things you should think about. But even before you think about PostgreSQL parameters you need to configure the networks your database instances shall be running in. In real life this is done by one of your network administrators and you will not have much to configure in this area….
When your go for AWS RDS you can very quickly bring up a database instance and start using it. I’ve written about my thoughts using this approach here and really encourage you to learn about a specific service in more detail before you start using it. If you want to have a managed service for PostgreSQL in AWS, you can go for AWS RDS for PostgreSQL and this service will be the topic for this…
In the last year working with/on AWS has become an almost daily task in my life as a consultant and trainer. From a trainer perspective there is not much to say about it because we use a very limited amount of services (EC2, mostly) and we have a limited amount of trainers that use the platform to deliver our trainings. When the amount of services you use is small and the amount of people managing…
A recent comment on the blog post about PostgreSQL default privileges is the reason for this little post: “I’d love to know where postgres stores default privileges?”. Well, all the information about privileges should be stored somewhere in the catalog so let’s check where that information could be.
When you go for AWS EC2 instances to host your PostgreSQL deployments and you want to rapidly clone PostgreSQL instances for development or testing purposes you can make use of AWS EBS snapshots. In this post we’ll look at how you can quickly spin up EC2 instances that use these snapshots as a base for new PostgreSQL clusters. Although we’ll be using the AWS console to show how this can be done you should use…
A common issue with insert only tables in PostgreSQL is, that autovacuum well never kick in as the formula for autovacuum considers obsoleted tuples since the last vacuum but not the number of inserted tuples. Because of this you usually run a manual vacuum when a table is bulk loaded right after the load or you schedule regular vacuums for tables you know are insert only. PostgreSQL 13 will finally solve that issue because autovacuum…
In the last post we had a look on how you can use AWS Storage Gateway as File gateway to store your PostgreSQL backups safely offsite on AWS S3. Another method of doing that would be to use “Cached Volume gateway” instead of the File gateway we used in the last post. The volume gateways does not provide access via NFS or SMB but does provide a volume over iSCSI and the on-prem machines will…
During tests in Oracle 19c I recently experienced this: [email protected]@orcl> select * from demo4 where m=103; [email protected]@orcl> select * from table(dbms_xplan.display_cursor); … ————————————————————————— | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | ————————————————————————— | 0 | SELECT STATEMENT | | | | 26439 (100)| | |* 1 | TABLE ACCESS FULL| DEMO4 | 1 | 10 | 26439 (14)| 00:00:02 | ————————————————————————— –> The costs of the full table…
In the last post we had a quick look at AWS Kinesis data streams and how you can push data to AWS S3 using AWS Firehose. Another great AWS service is AWS Storage Gateway and in this post we’ll use that to push our PostgreSQL backups to AWS. The primary usage of AWS Storage Gateway is to extend you local storage to AWS so that you do not have to extend your local storage on…
