Susan Hurst writes:
> Error from Postgres server log (postgresql-2019-08-16_140110.log):
> 2019-08-16 14:04:24 CDT ERROR: relation "devops.subscribers" does not
> exist
> 2019-08-16 14:04:24 CDT STATEMENT: create trigger subscribers_iur_trg
> instead of update
>
On 8/16/19 3:45 PM, Susan Hurst wrote:
We're using the 9.5.14 in the sandbox to extract data and objects from
the pgdump that was created in the 9.5.0 version. Hope I answered your
question correctly. If not, let me know and I'll try again.
As Rob pointed out I was wanting to know what pg_bi
On 8/16/19 4:45 PM, Susan Hurst wrote:
We're using the 9.5.14 in the sandbox to extract data and objects from
the pgdump that was created in the 9.5.0 version. Hope I answered
your question correctly. If not, let me know and I'll try again.
Our biggest concern is that there may be other si
We're using the 9.5.14 in the sandbox to extract data and objects from
the pgdump that was created in the 9.5.0 version. Hope I answered your
question correctly. If not, let me know and I'll try again.
Our biggest concern is that there may be other silent issues that we
have not yet discover
On 8/16/19 3:18 PM, Susan Hurst wrote:
Production version:
PostgreSQL 9.5.0 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.4.7
20120313 (Red Hat 4.4.7-16), 64-bit
Sandbox version:
"PostgreSQL 9.5.14, compiled by Visual C++ build 1800, 64-bit"
I going to say it has something to do with this
Production version:
PostgreSQL 9.5.0 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.4.7
20120313 (Red Hat 4.4.7-16), 64-bit
Sandbox version:
"PostgreSQL 9.5.14, compiled by Visual C++ build 1800, 64-bit"
---
Susan E Hurst
Principal Consultant
Brook
On 8/16/19 1:00 PM, Susan Hurst wrote:
The dump command used by the DBA to create the pgdump file is:
pg_dump --clean --if-exists --create --format=plain --no-owner
--no-tablespaces \
--file=${BKUPDIR}/${TS}.${USER}.pg 2>&1 \
| tee -a ${LOGDIR}/${TS}_biar_dump.log
No
The dump command used by the DBA to create the pgdump file is:
pg_dump --clean --if-exists --create --format=plain --no-owner
--no-tablespaces \
--file=${BKUPDIR}/${TS}.${USER}.pg 2>&1
\
| tee -a ${LOGDIR}/${TS}_biar_dump.log
No noticeable diffe
On 8/16/19 11:27 AM, Susan Hurst wrote:
What scenarios can cause a single trigger to be omitted when populating
an empty database from a pgdump file?
We have nightly backups of our production database that we load into a
fresh, empty database in our sandbox using the pgdump file.
psql.exe -h
What scenarios can cause a single trigger to be omitted when populating
an empty database from a pgdump file?
We have nightly backups of our production database that we load into a
fresh, empty database in our sandbox using the pgdump file.
psql.exe -h localhost -U mi601db -p 5432 -o
C:db_cr
10 matches
Mail list logo
