Skip to content

compute: Why is health_check table in public schema instead of neon? #12830

@levin-kitty

Description

@levin-kitty

Current behavior

When compute starts, a health_check table is automatically created in the public schema:

CREATE TABLE public.health_check ( id pg_catalog.int4 primary key generated by default as identity, updated_at pg_catalog.timestamptz default pg_catalog.now() );

Question

I noticed this is the only system table in public schema, while others use neon:

  • neon.neon_perf_counters
  • neon.drop_subscriptions_done
  • public.health_check ← why here?

Was this intentional? I'm wondering if there's a specific reason for putting it in public:

  • Does it need to be accessible without schema qualification?
  • Is there a compatibility reason?
  • Or would it make sense to move it to neon schema for consistency?

Just curious about the design decision here!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions