Hi,
haven’t tested it yet but maybe I can get a quick answer here.
We have discussed the following scenario.
Few nodes as streaming replication cluster all in sync with taking backup
only from one dedicated node. Now that node which is responsible for the backups
goes down. For sure I have a full
Hi Dirk,
Yes, this will work fine. You can use the existing backup to restore it on
the new node and use the WAL archives from new node for the recovery
purpose. As a best practice, I would suggest setting the parameter
"recovery_target_timeline=latest" in your recovery command to ensure the
recov
On 7/13/20 7:37 PM, Adrian Klaver wrote:
On 7/13/20 2:56 PM, Ron wrote:
On 7/13/20 2:32 PM, Adrian Klaver wrote:
On 7/13/20 12:12 PM, Julie Nishimura wrote:
Hello there,
One of our PostgreSQL 9.4.1 databases has been backed up as *.gz file
with the compression 9 "pg_dump -Z 9". What is the r
On 7/13/20 2:56 PM, Ron wrote:
On 7/13/20 2:32 PM, Adrian Klaver wrote:
On 7/13/20 12:12 PM, Julie Nishimura wrote:
Hello there,
One of our PostgreSQL 9.4.1 databases has been backed up as *.gz
file with the compression 9 "pg_dump -Z 9". What is the right format
of restore this file when nee
On 7/13/20 2:32 PM, Adrian Klaver wrote:
On 7/13/20 12:12 PM, Julie Nishimura wrote:
Hello there,
One of our PostgreSQL 9.4.1 databases has been backed up as *.gz file
with the compression 9 "pg_dump -Z 9". What is the right format of
restore this file when needed? Can I run the restore from
On 7/13/20 12:12 PM, Julie Nishimura wrote:
Hello there,
One of our PostgreSQL 9.4.1 databases has been backed up as *.gz file
with the compression 9 "pg_dump -Z 9". What is the right format of
restore this file when needed? Can I run the restore from a compressed
file or I need to unzip the
Hello there,
One of our PostgreSQL 9.4.1 databases has been backed up as *.gz file with the
compression 9 "pg_dump -Z 9". What is the right format of restore this file
when needed? Can I run the restore from a compressed file or I need to unzip
the file first, then run pg_restore? Thanks
sivapostg...@yahoo.com schrieb am 25.02.2020 um 02:55:
> Can u suggest a good backup solution for a windows installation ?
> Looks like the suggested two [ pgbarman, pgbackrest ] works only in
> Linux.
pg_probackup provides Windows binaries:
https://github.com/postgrespro/pg_probackup/
We do have plans to move to Linux in the future after the successful
implementation of at least 4 or 5 projects. Till then we want to keep windows.
We were (are) using SQL Server (also) and this is our first one with Postgres.
With our manpower, we feel tough to switch two things (Database &
On 24/2/20 4:18 pm, Dor Ben Dov wrote:
>
> Hi All,
>
>
>
> What is your backup and restore solution in production when working
> with Postgres ?
>
> (+ if you can say few words why you picked this X solution instead of
> others)
>
This is the THIRD time you've asked the same question with minimal
Greetings,
* sivapostg...@yahoo.com (sivapostg...@yahoo.com) wrote:
> HiCan u suggest a good backup solution for a windows installation ? Looks
> like the suggested two [ pgbarman, pgbackrest ] works only in Linux.
While it's certainly something we'd like to do, we haven't ported
pgbackrest to
HiCan u suggest a good backup solution for a windows installation ? Looks
like the suggested two [ pgbarman, pgbackrest ] works only in Linux.
On Tuesday, 25 February, 2020, 01:46:33 am IST, Stephen Frost
wrote:
Greetings,
* Dor Ben Dov (dor.ben-...@amdocs.com) wrote:
> What is your
Greetings,
* Dor Ben Dov (dor.ben-...@amdocs.com) wrote:
> What is your backup and restore solution in production when working with
> Postgres ?
> (+ if you can say few words why you picked this X solution instead of others)
I'd recommend pgbackrest- https://www.pgbackrest.org, it's got lots of
Am 24.02.20 um 09:18 schrieb Dor Ben Dov:
Hi All,
What is your backup and restore solution in production when working
with Postgres ?
most of our customers using Barman: https://www.pgbarman.org/
Regards, Andreas
--
2ndQuadrant - The PostgreSQL Support Company.
www.2ndQuadrant.com
Hi All,
What is your backup and restore solution in production when working with
Postgres ?
(+ if you can say few words why you picked this X solution instead of others)
Regards,
Dor
This email and the information contained herein is proprietary and confidential
and subject to the Amdocs Email
-k option is kept precisely for this. The upgrades are pretty fast, but still
with some downtime. may be 30-45 min tops.
n, and then leave them to connect (200 GB of
> data), because it is too long.
>
> Is there any way to upgrade PG and databases without backup/restore?
Yes, you can use pg_upgrade. However it will still copy 200GB (but using a
filecopy, not dump/restore) so it could still take some
rs, make a dumpall, upgrade, restore them
all in new version, and then leave them to connect (200 GB of data),
because it is too long.
Is there any way to upgrade PG and databases without backup/restore?
Maybe the solution is to upgrade slave without sync the data changes
before; and if all is ne
Adrian Klaver writes:
> On 10/24/19 2:58 PM, stan wrote:
>> So, it appears that this means that the function cannot be found, even if it
>> is in the new
>> (default) schema.
> The original error was not about finding the function it was about not
> finding the table in the function:
> psql:ta
On 10/24/19 2:58 PM, stan wrote:
On Thu, Oct 24, 2019 at 07:40:29AM -0700, Adrian Klaver wrote:
On 10/24/19 7:32 AM, stan wrote:
On Thu, Oct 24, 2019 at 07:04:11AM -0700, Adrian Klaver wrote:
On 10/24/19 3:52 AM, stan wrote:
I have a very confusing isse. I am trying to backup and restre a
On Thu, Oct 24, 2019 at 07:40:29AM -0700, Adrian Klaver wrote:
> On 10/24/19 7:32 AM, stan wrote:
> > On Thu, Oct 24, 2019 at 07:04:11AM -0700, Adrian Klaver wrote:
> > > On 10/24/19 3:52 AM, stan wrote:
> > > >
> > > >
> > > > I have a very confusing isse. I am trying to backup and restre a si
On 10/24/19 7:32 AM, stan wrote:
On Thu, Oct 24, 2019 at 07:04:11AM -0700, Adrian Klaver wrote:
On 10/24/19 3:52 AM, stan wrote:
I have a very confusing isse. I am trying to backup and restre a signle
table .
first I dump the table.
Actually you are just dumping the table data.
More below
On Thu, Oct 24, 2019 at 07:04:11AM -0700, Adrian Klaver wrote:
> On 10/24/19 3:52 AM, stan wrote:
> >
> >
> > I have a very confusing isse. I am trying to backup and restre a signle
> > table .
> >
> > first I dump the table.
>
> Actually you are just dumping the table data.
>
> More below.
>
On 10/24/19 3:52 AM, stan wrote:
I have a very confusing isse. I am trying to backup and restre a signle
table .
first I dump the table.
Actually you are just dumping the table data.
More below.
Script started on 2019-10-24 06:29:12-0400
]0;stan@smokey: ~stan@smokey:~$ pg_dump -a --tab
On Thu, Oct 24, 2019 at 07:57:14AM -0500, Ron wrote:
> Why did you do "\i task_instance.dump" instead of "pg_restore"?
Ah, that may be the root of my problem. I had in the back of my mind that
the result of a pg_dump was a free standing SQL script, but that my be
exactly what is going on. I will
I have a very confusing isse. I am trying to backup and restre a signle
table .
first I dump the table.
Script started on 2019-10-24 06:29:12-0400
]0;stan@smokey: ~stan@smokey:~$ pg_dump -a --table task_instance >
task_instance.dump
Then I connect to the db, and verify that things are as
Oh it is the one we are working on.
One of my team members brought up this issue from a job where we worked on
a vendor designed one.
I am convince we do not have an issue now.
Thanks for your expertise.
On Tue, Oct 22, 2019 at 4:42 PM Adrian Klaver
wrote:
> On 10/22/19 1:35 PM, stan wrote:
On 10/22/19 1:35 PM, stan wrote:
On Tue, Oct 22, 2019 at 12:48:41PM -0700, Adrian Klaver wrote:
On 10/22/19 10:48 AM, stan wrote:
Please reply to list also:
Ccing list.
Sorry if my description was not clear.
No, we do not mix test, and production data. Let me try to clarify the
question. L
On Tue, Oct 22, 2019 at 12:48:41PM -0700, Adrian Klaver wrote:
> On 10/22/19 10:48 AM, stan wrote:
> Please reply to list also:
> Ccing list.
>
>
> >
> > Sorry if my description was not clear.
> >
> > No, we do not mix test, and production data. Let me try to clarify the
> > question. Looking
On 10/22/19 10:48 AM, stan wrote:
Please reply to list also:
Ccing list.
Sorry if my description was not clear.
No, we do not mix test, and production data. Let me try to clarify the
question. Looking at a pg_dump, I see the following:
CREATE SEQUENCE public.customer_key_serial
START
dencies on keys developed from sequences after a
backup/restore cycle,
Will I potentially have these issues? If so, what can I do different to
avoid this being an issue?
It is not clear to me what you are doing:
1) Are you using pg_dump/pg_restore to populate a database?
If so it will take c
nces after a
backup/restore cycle,
Will I potentially have these issues? If so, what can I do different to
avoid this being an issue?
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
32 matches
Mail list logo
