[PG Bug reporting form <noreply@postgresql.org>]

The following bug has been logged on the website:

Bug reference:      15338
Logged by:          Oleg
Email address:      nekomata@olegk.ca
PostgreSQL version: 10.4
Operating system:   ubuntu 18.04
Description:        

for instance, there is a table "analytics.user_snapshot_data"
and it exists in its schema... 

when i do the restore here what is in the script:
--
-- PostgreSQL database dump
--

-- Dumped from database version 10.5 (Ubuntu 10.5-1.pgdg16.04+1)
-- Dumped by pg_dump version 10.5 (Ubuntu 10.5-1.pgdg16.04+1)

SET statement_timeout = 0;
SET lock_timeout = 0;
SET idle_in_transaction_session_timeout = 0;
SET client_encoding = 'UTF8';
SET standard_conforming_strings = on;
SELECT pg_catalog.set_config('search_path', '', false);
SET check_function_bodies = false;
SET client_min_messages = warning;
SET row_security = off;

--
-- Data for Name: user_snapshot_data; Type: TABLE DATA; Schema: analytics;
Owner: XXXXXXX
--

SET SESSION AUTHORIZATION DEFAULT;

ALTER TABLE user_snapshot_data DISABLE TRIGGER ALL;

COPY analytics.user_snapshot_data (report_date, user_id, company_id, tasks,
events) FROM stdin;
..... [data here] ....
-------------------------------------------------------------------------------------------------------------------

that fails with 
ERROR:  relation "user_snapshot_data" does not exist

so basically "ALTER TABLE user_snapshot_data DISABLE TRIGGER ALL;"
is missing proper schema.