Re: [GENERAL] recovery of a windows archive in linux

Adrian, Jim: thanks a lot for your help. I'll replay my logs on a Windows machine very similar to the one that was hosting my db and see how it goes before I make a pg_dump for Linux. 2015-04-13 21:49 GMT-04:00 Adrian Klaver : > On 04/13/2015 04:37 PM, Guillaume Drolet wrote: > &

[GENERAL] recovery of a windows archive in linux

Dear list, I have a base backup and archive logs from a Windows 7 PGSQL 9.3 install. The machine OS disk started to show signs of failure so I replaced it and now I want to switch for a Linux system. My question is: will I be able to play my archive logs and point-in-time recover on the Linux mac

Re: [GENERAL] Slow trigger on insert: alternative solutions?

ian Klaver : > On 03/30/2015 06:04 AM, Guillaume Drolet wrote: > >> Hello, >> >> I need your help speeding up the procedure I will explain below. I am >> looking for improvements to my method or different approaches/ideas to >> would help in this matter. >&

[GENERAL] Slow trigger on insert: alternative solutions?

Hello, I need your help speeding up the procedure I will explain below. I am looking for improvements to my method or different approaches/ideas to would help in this matter. I have a set of DBF files that I load into my database using a plpython function and a call to ogr2ogr (http://www.gdal.or

Re: [GENERAL] Sequences not moved to new tablespace

2015-02-24 10:39 GMT-05:00 Albe Laurenz : > Guillaume Drolet wrote: > >> If you want to move a whole database to a different tablespace (the > only reason > >> I can think of for doing what you are trying to so), use the command > >> ALTER DATABASE ... SET TABLE

Re: [GENERAL] Sequences not moved to new tablespace

2015-02-24 10:18 GMT-05:00 Adrian Klaver : > On 02/24/2015 07:10 AM, Guillaume Drolet wrote: > >> >> >> > >> >> So how did all this stuff get into the non-default tablespace in the >> first place? >> >> >> Stuff got there usi

Re: [GENERAL] Sequences not moved to new tablespace

2015-02-24 10:32 GMT-05:00 Tom Lane : > Adrian Klaver writes: > > On 02/24/2015 07:10 AM, Guillaume Drolet wrote: > >> That makes sense. I will give it a try. Thanks. > > > Alright, now I am thoroughly confused:) I thought this is how you to > > this point, usin

Re: [GENERAL] Sequences not moved to new tablespace

2015-02-24 10:06 GMT-05:00 Adrian Klaver : > On 02/24/2015 05:06 AM, Guillaume Drolet wrote: > >> >> >> 2015-02-24 7:07 GMT-05:00 Guillaume Drolet > <mailto:droletguilla...@gmail.com>>: >> >> >> >> 2015-02-23 14:14 GMT

Re: [GENERAL] Sequences not moved to new tablespace

2015-02-24 8:45 GMT-05:00 Albe Laurenz : > Guillaume Drolet wrote: > > Digging a little more, I found that not only sequences were not moved > but also many tables in > > pg_catalog are still in my old tablespace. This is expected since the > query in the SQL files I used t

Re: [GENERAL] Sequences not moved to new tablespace

2015-02-24 7:07 GMT-05:00 Guillaume Drolet : > > > 2015-02-23 14:14 GMT-05:00 Adrian Klaver : > > On 02/23/2015 10:08 AM, Guillaume Drolet wrote: >> >>> Hello, >>> >>> I moved all my tables and indexes from one tablespace to pg_default using &

Re: [GENERAL] Sequences not moved to new tablespace

2015-02-23 14:14 GMT-05:00 Adrian Klaver : > On 02/23/2015 10:08 AM, Guillaume Drolet wrote: > >> Hello, >> >> I moved all my tables and indexes from one tablespace to pg_default using >> >> ALTER TABLE ... SET TABLESPACE pg_default; >> ALTER INDEX ...

[GENERAL] Sequences not moved to new tablespace

Hello, I moved all my tables and indexes from one tablespace to pg_default using ALTER TABLE ... SET TABLESPACE pg_default; ALTER INDEX ... SET TABLESPACE pg_default; Some 2500 files were moved to pg_default but 461 files remain in the tablespace and so I cannot drop it. When I query, for examp

Re: [GENERAL] Cluster seems broken after pg_basebackup

and running again. >> >> PS. I was thinking of reinstalling PGSQL over my current install but >> keeping my PGDATA. I've done it in the past for fixing problems with >> starting the service and it worked. What do you think? >> > > You could try it, but as G

Re: [GENERAL] Starting new cluster from base backup

2015-02-18 16:11 GMT-05:00 Adrian Klaver : > On 02/18/2015 11:51 AM, Guillaume Drolet wrote: > >> >> >> 2015-02-18 13:40 GMT-05:00 Adrian Klaver > <mailto:adrian.kla...@aklaver.com>>: >> >> On 02/18/2015 10:24 AM, Guillaume Drolet wrote: >&

Re: [GENERAL] Starting new cluster from base backup

2015-02-18 13:40 GMT-05:00 Adrian Klaver : > On 02/18/2015 10:24 AM, Guillaume Drolet wrote: > >> >> >> 2015-02-18 11:06 GMT-05:00 Adrian Klaver > <mailto:adrian.kla...@aklaver.com>>: >> >> > >> So is E:\ a network drive shared by bo

Re: [GENERAL] Starting new cluster from base backup

2015-02-18 11:06 GMT-05:00 Adrian Klaver : > On 02/18/2015 04:26 AM, Guillaume Drolet wrote: > >> >> >> 2015-02-17 17:14 GMT-05:00 Adrian Klaver > <mailto:adrian.kla...@aklaver.com>>: >> >> >> On 02/17/2015 06:54 AM, Guillaume Drolet wr

Re: [GENERAL] Starting new cluster from base backup

2015-02-17 17:14 GMT-05:00 Adrian Klaver : > On 02/17/2015 06:54 AM, Guillaume Drolet wrote: > >> Adrian: thanks for this information. >> >> I tried running pg_basebackup in plain format with option -X stream >> (pg_basebackup -D "F:\208376PT\db" -X stream

Re: [GENERAL] Starting new cluster from base backup

3. Is there another way to circumvent the problem and still be able to backup using -X stream and plain format when tablespace have been created elsewhere? Thanks! 2015-02-17 9:54 GMT-05:00 Guillaume Drolet : > Adrian: thanks for this information. > > I tried running pg_basebackup in pla

Re: [GENERAL] Starting new cluster from base backup

his? Thanks. 2015-02-16 15:21 GMT-05:00 Adrian Klaver : > On 02/16/2015 11:31 AM, Guillaume Drolet wrote: > >> Dear listers, >> >> I want to move a cluster from one machine to another. I used >> pg_basebackup to create an archive and copied/extracted it over the ol

[GENERAL] Starting new cluster from base backup

Dear listers, I want to move a cluster from one machine to another. I used pg_basebackup to create an archive and copied/extracted it over the old PGDATA location on the new machine (the server was stopped). If I start pgsql I get these messages in my log file: 2015-02-16 14:29:12 EST LOG: datab

Re: [GENERAL] Cluster seems broken after pg_basebackup

> On 02/06/2015 05:03 AM, Guillaume Drolet wrote: > >> Hi, >> >> Yesterday I ran a pg_basebackup of my cluster. Since it has completed, >> my cluster doesn't work properly. I tried restarting the computer (or >> service) a few times but I always get the sa

Re: [GENERAL] Cluster seems broken after pg_basebackup

ning again. >> >> PS. I was thinking of reinstalling PGSQL over my current install but >> keeping my PGDATA. I've done it in the past for fixing problems with >> starting the service and it worked. What do you think? >> > > You could try it, but as Guillaume Dro

Re: [GENERAL] Cluster seems broken after pg_basebackup

Guillaume: the cluster I try to start is the one used with pg_basebackup, not the result of the backup. 2015-02-09 12:51 GMT-05:00 Guillaume Lelarge : > 2015-02-09 18:40 GMT+01:00 Guillaume Drolet : > >> I tried starting the cluster again. Once again everything looked fine at >>

Re: [GENERAL] Cluster seems broken after pg_basebackup

d not be %s. This is not of much help to me. I hope these additional bits of information can help someone figuring out a solution to get my cluster up and running again. PS. I was thinking of reinstalling PGSQL over my current install but keeping my PGDATA. I've done it in the past for

Re: [GENERAL] Cluster seems broken after pg_basebackup

2015-02-07 1:24 GMT-05:00 Guillaume Lelarge : > Le 6 févr. 2015 17:31, "Adrian Klaver" a > écrit : > > > > On 02/06/2015 05:03 AM, Guillaume Drolet wrote: > >> > >> Hi, > >> > >> Yesterday I ran a pg_basebackup of my cluster. Since

Re: [GENERAL] Cluster seems broken after pg_basebackup

:03 AM, Guillaume Drolet wrote: > >> Hi, >> >> Yesterday I ran a pg_basebackup of my cluster. Since it has completed, >> my cluster doesn't work properly. I tried restarting the computer (or >> service) a few times but I always get the same messages in my logs (it

[GENERAL] Cluster seems broken after pg_basebackup

Hi, Yesterday I ran a pg_basebackup of my cluster. Since it has completed, my cluster doesn't work properly. I tried restarting the computer (or service) a few times but I always get the same messages in my logs (it's in French. If someone is willing to help me I can try to translate the logs. Jus

[GENERAL] Error: could not read symbolic link "pg_tblspc/940585". No such file or directory

Dear list users, I moved a database from a tablespace I had created to pg_default using: ALTER DATABASE mydatabase SET TABLESPACE pg_default; After the database was fully copied to a new directory under PGDATA/base, I deleted the symbolic link to the old tablespace using (in Windows) rmdir PGDAT

Re: [GENERAL] Cluster recovery - FATAL: database files are incompatible with server. Different PG_CONTROL_VERSION for cluster and server.

ge > From: Adrian Klaver > Date:04-17-2014 20:36 (GMT-05:00) > To: Guillaume Drolet ,pgsql-general@postgresql.org > Subject: Re: [GENERAL] Cluster recovery - FATAL: database files are > incompatible with server. Different PG_CONTROL_VERSION for cluster and > server. > &

Re: [GENERAL] Cluster recovery - FATAL: database files are incompatible with server. Different PG_CONTROL_VERSION for cluster and server.

nk it with my databases on that disk? 2014-04-17 20:29 GMT-04:00 Adrian Klaver : > On 04/17/2014 01:29 PM, Guillaume Drolet wrote: >> >> Dear list users, >> >> For some tests, I installed a new cluster with different parameters >> than the ones I had used a while ago

[GENERAL] Cluster recovery - FATAL: database files are incompatible with server. Different PG_CONTROL_VERSION for cluster and server.

Dear list users, For some tests, I installed a new cluster with different parameters than the ones I had used a while ago to create the cluster I use for my day-to-day activities (let's call it my main cluster). I used initdb --no-locale -E UTF8 -D . Then I used pg_ctl -D to start my new cluster.