Re: I have no idea why pg_dump isn't dumping all of my data

i just did a dump of a db which was owned by postgres but some tables owned
by other users and it ran fine.
I am not sure of that nanoscopic extension though.

*******************************
createdb -e foobar;

postgres=# \c foobar
You are now connected to database "foobar" as user "postgres".
foobar=# set role demo;
SET
foobar=> create table xx(id int);
CREATE TABLE
foobar=> \dt
List of relations
Schema | Name | Type | Owner
--------+------+-------+-------
public | xx | table | demo
(1 row)

foobar=> insert into xx values (1);
INSERT 0 1
foobar=> \dt
List of relations
Schema | Name | Type | Owner
--------+------+-------+-------
public | xx | table | demo
(1 row)

foobar=> \l
List of databases
Name | Owner | Encoding | Collate | Ctype | Access
privileges
-----------+----------+----------+------------+------------+-----------------------
demo | demo_rw | UTF8 | en_US.utf8 | en_US.utf8 |
foobar | postgres | UTF8 | en_US.utf8 | en_US.utf8 |
postgres | postgres | UTF8 | en_US.utf8 | en_US.utf8 |
template0 | postgres | UTF8 | en_US.utf8 | en_US.utf8 | =c/postgres
+
| | | | |
postgres=CTc/postgres
template1 | postgres | UTF8 | en_US.utf8 | en_US.utf8 | =c/postgres
+
| | | | |
postgres=CTc/postgres
(5 rows)
*******************************

*******************************
pg_dump --file=nanoscopic_db_127_0_0_1-2021_05_21_10_25_28-dump.sql
--dbname=foobar --clean --create --if-exists --username=demo -v
--host=127.0.0.1 --port=5432

... last lines from the verbose dump

pg_dump: dropping DATABASE foobar
pg_dump: creating DATABASE "foobar"
pg_dump: connecting to new database "foobar"
pg_dump: creating TABLE "public.xx"
pg_dump: processing data for table "public.xx"
pg_dump: dumping contents of table "public.xx"

CREATE DATABASE foobar WITH TEMPLATE = template0 ENCODING = 'UTF8' LOCALE =
'en_US.utf8';

ALTER DATABASE foobar OWNER TO postgres;

\connect foobar

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 xmloption = content;
SET client_min_messages = warning;
SET row_security = off;

SET default_tablespace = '';

SET default_table_access_method = heap;

--
-- TOC entry 200 (class 1259 OID 26105)
-- Name: xx; Type: TABLE; Schema: public; Owner: demo
--

CREATE TABLE public.xx (
id integer
);

ALTER TABLE public.xx OWNER TO demo;

--
-- TOC entry 2232 (class 0 OID 26105)
-- Dependencies: 200
-- Data for Name: xx; Type: TABLE DATA; Schema: public; Owner: demo
--

COPY public.xx (id) FROM stdin;
1
\.

-- Completed on 2021-05-21 15:54:08 IST

--
-- PostgreSQL database dump complete
--
*******************************
works fine.
I do not know that extension(nanoscopic) though.

it is reading some tables in a public schema, but not even dumping the
schema.

yep, thats odd if it does not throw any errors, coz any errors wrt
permissions are thrown right away to console.

maybe someone with more exp would be able to help.

On Fri, 21 May 2021 at 15:32, Simon Connah <simon(dot)n(dot)connah(at)protonmail(dot)com>
wrote:

> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Friday, May 21st, 2021 at 10:55, Vijaykumar Jain <
> vijaykumarjain(dot)github(at)gmail(dot)com> wrote:
>
> Can you try dumping using verbose flag.
> -v
>
> Just want to confirm if the user has relevant permissions.
>
>
> On Fri, May 21, 2021, 3:04 PM Simon Connah <simon(dot)n(dot)connah(at)protonmail(dot)com>
> wrote:
>
>> Hi,
>>
>> I'm running the following command to dump my database:
>>
>> /usr/bin/pg_dump
>> --file=/home/simon/nanoscopic_db_127_0_0_1-2021_05_21_10_25_28-dump.sql
>> --dbname=nanoscopic_db --clean --create --if-exists
>> --username=nanoscopic_db_user --host=127.0.0.1 --port=5432
>>
>> and yet when I run that all I get in the SQL file is the following:
>>
>> https://gist.github.com/simonconnah/e1a15b1536b6e519b84481ae74f082bf
>>
>> I'm at a total loss. I've tried all the relevant looking command line
>> switches and nothing seems to dump the actual contents of the database. It
>> just dumps the extension command. Can anyone help me to figure this out
>> please? It is probably something stupid that I am doing wrong.
>>
>> Simon.
>>
>
> *pg_dump: *last built-in OID is 16383
> *pg_dump: *reading extensions
> *pg_dump: *identifying extension members
> *pg_dump: *reading schemas
> *pg_dump: *reading user-defined tables
> *pg_dump: *reading user-defined functions
> *pg_dump: *reading user-defined types
> *pg_dump: *reading procedural languages
> *pg_dump: *reading user-defined aggregate functions
> *pg_dump: *reading user-defined operators
> *pg_dump: *reading user-defined access methods
> *pg_dump: *reading user-defined operator classes
> *pg_dump: *reading user-defined operator families
> *pg_dump: *reading user-defined text search parsers
> *pg_dump: *reading user-defined text search templates
> *pg_dump: *reading user-defined text search dictionaries
> *pg_dump: *reading user-defined text search configurations
> *pg_dump: *reading user-defined foreign-data wrappers
> *pg_dump: *reading user-defined foreign servers
> *pg_dump: *reading default privileges
> *pg_dump: *reading user-defined collations
> *pg_dump: *reading user-defined conversions
> *pg_dump: *reading type casts
> *pg_dump: *reading transforms
> *pg_dump: *reading table inheritance information
> *pg_dump: *reading event triggers
> *pg_dump: *finding extension tables
> *pg_dump: *finding inheritance relationships
> *pg_dump: *reading column info for interesting tables
> *pg_dump: *finding the columns and types of table "public.blog_user"
> *pg_dump: *finding default expressions of table "public.blog_user"
> *pg_dump: *finding check constraints for table "public.blog_user"
> *pg_dump: *finding the columns and types of table "public.blog"
> *pg_dump: *finding default expressions of table "public.blog"
> *pg_dump: *finding the columns and types of table "public.blog_post"
> *pg_dump: *finding default expressions of table "public.blog_post"
> *pg_dump: *finding check constraints for table "public.blog_post"
> *pg_dump: *finding the columns and types of table
> "public.blog_post_comment"
> *pg_dump: *finding default expressions of table
> "public.blog_post_comment"
> *pg_dump: *finding the columns and types of table "public.blog_page"
> *pg_dump: *finding default expressions of table "public.blog_page"
> *pg_dump: *finding the columns and types of table
> "public.blog_user_permissions"
> *pg_dump: *finding default expressions of table
> "public.blog_user_permissions"
> *pg_dump: *flagging inherited columns in subtables
> *pg_dump: *reading indexes
> *pg_dump: *reading indexes for table "public.blog_user"
> *pg_dump: *reading indexes for table "public.blog"
> *pg_dump: *reading indexes for table "public.blog_post"
> *pg_dump: *reading indexes for table "public.blog_post_comment"
> *pg_dump: *reading indexes for table "public.blog_page"
> *pg_dump: *reading indexes for table "public.blog_user_permissions"
> *pg_dump: *flagging indexes in partitioned tables
> *pg_dump: *reading extended statistics
> *pg_dump: *reading constraints
> *pg_dump: *reading triggers
> *pg_dump: *reading rewrite rules
> *pg_dump: *reading policies
> *pg_dump: *reading row security enabled for table
> "public.blog_user_blog_user_id_seq"
> *pg_dump: *reading policies for table "public.blog_user_blog_user_id_seq"
> *pg_dump: *reading row security enabled for table "public.blog_user"
> *pg_dump: *reading policies for table "public.blog_user"
> *pg_dump: *reading row security enabled for table
> "public.blog_blog_id_seq"
> *pg_dump: *reading policies for table "public.blog_blog_id_seq"
> *pg_dump: *reading row security enabled for table "public.blog"
> *pg_dump: *reading policies for table "public.blog"
> *pg_dump: *reading row security enabled for table
> "public.blog_post_blog_post_id_seq"
> *pg_dump: *reading policies for table "public.blog_post_blog_post_id_seq"
> *pg_dump: *reading row security enabled for table "public.blog_post"
> *pg_dump: *reading policies for table "public.blog_post"
> *pg_dump: *reading row security enabled for table
> "public.blog_post_comment_blog_post_comment_id_seq"
> *pg_dump: *reading policies for table
> "public.blog_post_comment_blog_post_comment_id_seq"
> *pg_dump: *reading row security enabled for table
> "public.blog_post_comment"
> *pg_dump: *reading policies for table "public.blog_post_comment"
> *pg_dump: *reading row security enabled for table
> "public.blog_page_blog_page_id_seq"
> *pg_dump: *reading policies for table "public.blog_page_blog_page_id_seq"
> *pg_dump: *reading row security enabled for table "public.blog_page"
> *pg_dump: *reading policies for table "public.blog_page"
> *pg_dump: *reading row security enabled for table
> "public.blog_user_permissions_blog_user_permissions_id_seq"
> *pg_dump: *reading policies for table
> "public.blog_user_permissions_blog_user_permissions_id_seq"
> *pg_dump: *reading row security enabled for table
> "public.blog_user_permissions"
> *pg_dump: *reading policies for table "public.blog_user_permissions"
> *pg_dump: *reading publications
> *pg_dump: *reading publication membership
> *pg_dump: *reading subscriptions
> *pg_dump: *reading large objects
> *pg_dump: *reading dependency data
> *pg_dump: *saving encoding = UTF8
> *pg_dump: *saving standard_conforming_strings = on
> *pg_dump: *saving search_path =
> *pg_dump: *saving database definition
> *pg_dump: *dropping DATABASE nanoscopic_db
> *pg_dump: *creating DATABASE "nanoscopic_db"
> *pg_dump: *connecting to new database "nanoscopic_db"
> *pg_dump: *creating EXTENSION "nanoscopic"
> *pg_dump: *creating COMMENT "EXTENSION nanoscopic"
> *pg_dump: *creating ACL "DATABASE nanoscopic_db"
>

--
Thanks,
Vijay
Mumbai, India