![]() ![]() JOIN pg_namespace dependent_ns ON dependent_ns.oid = dependent_view.relnamespaceĭependent_ns.nspname as dependent_schema,ĭependent_view.relname as dependent_view, JOIN pg_class as dependent_view ON pg_rewrite.ev_class = dependent_view.oid JOIN pg_rewrite ON pg_depend.objid = pg_rewrite.oid Get a list of views that have dependencies on other views Here's a query that will bring up your materialized views as well and show you the views' dependencies. LEFT JOIN pg_catalog.pg_stat_all_tables s ON (c.oid = s.relid) LEFT JOIN pg_catalog.pg_attribute a ON (c.oid = a.attrelid AND a.attnum > 0 AND NOT a.attisdropped) THEN pg_catalog.pg_get_viewdef(c.oid, true) Pg_catalog.obj_description(c.oid, 'pg_class') AS comments, If you want more detail you can modify the following to suit your needs: SELECT n.nspname AS table_schema, LEFT JOIN pg_catalog.pg_namespace n ON (n.oid = c.relnamespace) One of the more interesting to me relates right back to those template databases.Pg_catalog.pg_get_userbyid(c.relowner) AS table_owner, The CREATE DATABASE command has a number of options, as you can see in the documentation. Also, when you restore a database, PostgreSQL uses template0 to start that process (I’ll explain how and why once I learn).Īnd what about that postgres database? Well, that’s a default built into PostgreSQL so that tools always connect to a default database. What’s that? Well, in the event you completely mess up template1, template0 acts as a baseline. However, there’s more going on in PostgreSQL. You can add objects to template1, and then they will automatically exist in any other new database you create. The table template1 operates very similarly to model. In PostgreSQL, the same thing happens, but the database is called template1. In SQL Server, you have a system database called model used as a template when you create a new database. Since I know SQL Server, I’m going to compare what’s going on here, to what’s going on there. The command to create a database is quite simple: I don’t want to document every single possible method, so I had to pick one. ![]() I’m old, and I’m just more comfortable working on code within a dedicated coding tool as opposed to simply running it from the command line.For example, it plugs in very nicely to GitHub, so you can easily keep the code as you develop it up on GitHub ( go here if you want to see my VERY basic PostgreSQL code: ).I’m going to focus there, working primarily within Azure Data Studio (ADS). Finally, the SQL commands are available once you’re connected to PostgreSQL. You can do everything from a command line or use a graphical user interface (GUI) that lets you work with PostgreSQL. I could then back them up.Īs with any data management system, there are many ways to get this done. I needed to create a database and a couple of tables. However, I realized I had another thing I needed to do before I could begin learning – and teaching - backups. Now, what to do with it? In the first article in this series, I said I would start by learning about backups. You have an instance of PostgreSQL running locally (or you’re connected to the cloud). Data Types in PostgreSQL: Learning PostgreSQL with Grant.How to back up and restore with PostgreSQL: Learning PostgreSQL with Grant.Creating a Database and Tables in PostgreSQL: Learning PostgreSQL with Grant.Connecting to PostgreSQL: Learning PostgreSQL with Grant. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |