drizzle-kit introspect postgres db pg_stat_statement

[alexmondaini]

Hi everyone,

I am introspecting a postgres database from the public schema , and dizzle introspects even internal postgres tables like pg_stat_statements . I would not like to instrospect such tables that are managed by potgres itself. Additionaly after instropecting I also get an error for the oid datatype:

//TODO: failed to parse database type 'oid'
userid: unknown('userid')

I use typescript and my liniting complains about unknown

[amikofalvy]

@alexmondaini I am also using the pg_stat_statements extension (on NeonDB). The extension creates two tables 'pg_stat_statements' and 'pg_stat_statements_info'.

Since I don't want to manage those tables with my drizzle schema definition I've added them to the tablesFilter on my drizzle.config.ts file.

import { defineConfig } from 'drizzle-kit';

export default defineConfig({
  schema: './src/lib/db/schema.ts',
  dialect: 'postgresql',
  dbCredentials: {
    url: process.env.DATABASE_URL,
  },
  verbose: true,
  strict: true,
  out: './drizzle',
  tablesFilter: ['pg_stat_statements', 'pg_stat_statements_info'],
});

After I added these tables to the filter there were no more issues during any of the drizzle-kit commands such as introspect, generate, push.

I'm running "drizzle-kit": "0.23.2" and drizzle-orm 0.32.2

[alexmondaini]

hi to me this caused the effect of filtering in the tables, now I only have ['pg_stat_statements', 'pg_stat_statements_info'] in my schema

[alexmondaini]

running drizzle-kit 0.24.2 with orm 0.33.0

[amikofalvy]

Ah, you're right. I tried yesterday to introspect from my db and only got the tables defined within the filter array. But you can probably use this or similar parameters for your use case.

[alexmondaini]

this works great, but as of drizzle kit 0.27, if i run drizzle-kit migrate it will generate a migration as follows:

DROP VIEW pg_stat_statements;
DROP VIEW pg_stat_statements_info;

effectively i dont want to drop them but just ignore.