On Wed, Oct 19, 2016 at 6:15 AM, Ashish Chauhan
wrote:
> *2016-10-18 22:11:30 UTC [13107-1] FATAL: database files are incompatible
> with server*
>
> *2016-10-18 22:11:30 UTC [13107-2] DETAIL: The data directory was
> initialized by PostgreSQL version 9.6, which is not compatible with this
> ve
you can run select * from pg_stat_replication on master to check all the
salve stats.
On Fri, Jul 18, 2014 at 6:50 AM, Lists wrote:
> For reference:
> https://wiki.postgresql.org/wiki/Streaming_Replication
>
> Assume a master -> slave streaming replication configuration, Postgresql
> 9.2.
> Ass
What's the output when you try to login? Have your slave configured as a
standby server ?
On Mon, Aug 25, 2014 at 12:46 PM, Rajesh K wrote:
> Dear Sir,
>
> I have planned to configure PostgreSQL 9.2.4 database Master and Slave
> replication on Redhat Linux Server 6.As per the documentation i h
You can search from google,
https://www.google.com/search?q=mysql2pg&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a
On Sat, Jan 12, 2013 at 7:54 AM, Ken Tanzer wrote:
> I'm wondering if anyone can point me towards a good method for moving
> mysql data into Postgres? I'v
I have a long SQL with many join, the explain analyse output like
-> Hash Left Join (cost=197749705.15..5320438982425.18
rows=5245599776015 width=7542) (actual time=674.634..2645.293 rows=4568
loops=1)
Hash Cond: (p.id = ps.partner_id)
-> Merge Join (cost=197747693.55..788
Thanks for your reply.
On Mon, Feb 4, 2013 at 3:48 PM, Tom Lane wrote:
> You're worrying about the wrong thing entirely. The right thing to be
> worrying about is why are some of those row estimates off by four orders
> of magnitude, and what you can do to fix that. The planner will never
> d
You can combine warm standby and streaming, we do this in our product
database.
When the standby is to far from the master, the slave will try to use
restore_command to restore the database(warm standby), when the standby
catch up the master, the steaming will working again.
BTW: we use ominipitr.
On Fri, Mar 22, 2013 at 11:27 AM, Roberto Scattini <
roberto.scatt...@gmail.com> wrote:
>
>
> On Thursday, March 21, 2013, wd wrote:
> > You can combine warm standby and streaming, we do this in our product
> database.
> > When the standby is to far from the mas
You can try http://oracle-fdw.projects.postgresql.org/
On Wed, Apr 10, 2013 at 12:07 AM, kiran wrote:
> Hello,
>
> I am looking for an example on creating a DBLink from PostrgeSQL 9.2 to
> Oracle 11g.
> I tried the below link and for some reason the ODBC_Link installation is
> failing.
>
> FYI.,
On Sun, Jun 9, 2013 at 6:04 AM, wrote:
> Hi All,
>
>
>
> I have a problem with PostgreSQL 8.4. It was working perfectly fine but
> after the restart (within a couple of minutes) of my system whenever I
> login to PostgreSQL 8.4 (localhost:5432) it gives error as under:
>
>
>
> *Server doesn't
Try add these settings,
pause_at_recovery_target=true
recovery_target_inclusive=false
On Fri, Aug 9, 2013 at 4:09 PM, ascot.m...@gmail.com
wrote:
> Hi,
>
> I am trying PITR in a test machine (same PG version 9.2.4 same O/S Ubuntu
> 12.04 64 bit). All archived WAL files are shipped and saved i
Try this,
max_standby_archive_delay = 600s# max delay before canceling queries
# when reading WAL from archive;
# -1 allows indefinite delay
max_standby_streaming_delay = 600s # max delay before canceling
hi,
We have upgrade our database from PostgreSQL 9.2.4 to 9.3.2, use dump &
restore in a fresh db created by initdb.
Then use pg_basebackup created 2 slave db, the error occur when start the
database.
db1
[2013-12-19 04:00:56.882 CST 17956 52b1fef8.4624 1 0]LOG:
database system was interrup
On Thu, Dec 19, 2013 at 2:24 PM, Amit Langote wrote:
> "unexpected pageaddr" log entry in this case means the standby reached
> the end of existing WAL.
> So, just before connecting to walsender for streaming replication, it logs
> this.
>
Thanks for your reply. So this means I can safely omit t
On Thu, Dec 19, 2013 at 11:56 PM, bricklen wrote:
>
> On Thu, Dec 19, 2013 at 1:27 AM, wd wrote:
>
>>
>> On Thu, Dec 19, 2013 at 2:24 PM, Amit Langote wrote:
>>
>>> "unexpected pageaddr" log entry in this case means the standby reached
>>>
I found there is no option to disable sync for pg_log in pg_basebackup,
maybe there should be one option to disalbe it?
hi,
I'v try to make a base backup use pg_start_backup, pg_stop_backup and
rsync, but failed.
After run select pg_start_backup('label') on db server, I run rsync on
backup server, and got some errors like 'file has vanished: ', think
this should be ok since it's documented in the manual. Then
PostgreSQL 9.2.4
On Tue, Apr 22, 2014 at 1:58 PM, Michael Paquier
wrote:
>
>
>
> On Tue, Apr 22, 2014 at 1:28 PM, wd wrote:
>
>> I'v try to make a base backup use pg_start_backup, pg_stop_backup and
>> rsync, but failed.
>>
>> After run select pg_sta
hi,
I've try to restore Postgres to a specific time but failed.
The recovery.conf as bellow
restore_command='cp /t/xlog/%f %p'
recovery_target_time='2012-11-22 5:01:09 CST'
pause_at_recovery_target=true
recovery_target_inclusive=false
The basebackup was made at 2012-11-22 3:10 CST, I've copy wal
g file "00010028002E" from archive
[2012-11-22 18:50:54.920 CST 25744 50ae0334.6490 17 0]LOG: restored
log file "00010028002F" from archive
cp: cannot stat `/export/t/xlog/000100280030': No such file or
directory
cp: cannot stat `/export/t/xl
u ram wrote:
>
>
> On Fri, Nov 23, 2012 at 8:59 AM, wd wrote:
>
>> Thanks for your reply, the logs are something like bellow，postgres will
>> restore every wal log I put in the xlog directory，and then continues
>> waiting for next wal log. The postgres version is 9.1.6.
&
On Sun, Nov 25, 2012 at 4:25 AM, Jeff Janes wrote:
> On Sat, Nov 24, 2012 at 6:00 AM, wd wrote:
> > Yes, you are right, after set the two command, the recovery will stop at
> > that time.
> >
> > But there is an other question, how to make this recovered Postgres
I can't connect to postgres at that time.
On Mon, Nov 26, 2012 at 4:33 PM, Albe Laurenz wrote:
> wd wrote:
> > Logs are something like this:
> > [2012-11-24 21:51:33.591 CST 583 50b0d0e5.247 9 0]LOG: recovery
> has paused
> > [2012-11-24 21:51:33.591 C
On Mon, Nov 26, 2012 at 11:32 PM, Albe Laurenz wrote:
> wd wrote:
> >>> Logs are something like this:
> >>>
> >>> [2012-11-24 21:51:33.591 CST 583 50b0d0e5.247 9 0]LOG: recovery
> has paused
> >>> [2012-11-24 21:51:33.591 CST 583 5
On Tue, Nov 27, 2012 at 8:27 AM, Jeff Janes wrote:
> On Mon, Nov 26, 2012 at 12:23 PM, Kevin Grittner wrote:
> > Jeff Janes wrote:
> >
> >> FATAL: requested recovery stop point is before consistent recovery point
> >>
> >> I don't understand why are you not getting this message.
> >
> > Is it be
Only found one
http://interdbconnect.sourceforge.net/pgsql_fdw/pgsql_fdw-en.html working
for PostgreSQL 9.1.
hi,
>From pg_stat_activity I can find a query is at waiting state, and from
pg_locks and pg_class can find which relation the query is waiting for, But
how to find witch query is lock the relation?
I know how to do this, thanks.
On Fri, Dec 7, 2012 at 11:09 PM, Fabrízio de Royes Mello <
fabriziome...@gmail.com> wrote:
>
> On Fri, Dec 7, 2012 at 1:02 PM, wd wrote:
>
>> hi,
>>
>> From pg_stat_activity I can find a query is at waiting state, and from
>&g
Seems they fork from postgres, pgadmin and rename them to highgo and
hgadmin, but didn't announce this anywhere.
(Merlln, sorry for the individual mail)
On Tue, Dec 11, 2012 at 10:31 PM, Merlin Moncure wrote:
> On Mon, Dec 10, 2012 at 7:02 PM, Fan, Yi wrote:
> > To whom it my concern,
> >
> >
We encounter the same problem, and have to change to use copy command
On Wed, Dec 5, 2012 at 9:17 PM, James Cowell wrote:
> I'm using pg_bulkload to load large amounts of CSV data into a postgres
> database hourly.
>
> This database is replicated to a second node.
>
> Whenever a bulk load happe
hi,
wd_test=# \d t1
Table "public.t1"
Column | Type |Modifiers
+-+-
id | integer | not null default nextval('t1_id_seq'::regclass)
tag| text|
wd_test=# select * from t1;
Sorry, forget to say,
PostgreSQL 9.2.2 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.4.6
20110731 (Red Hat 4.4.6-3), 64-bit
psql (9.2.2)
On Fri, Dec 28, 2012 at 3:24 PM, wd wrote:
> hi,
>
> wd_test=# \d t1
> Table "public.t1&q
Oh, I see, thanks for your quick reply.
On Fri, Dec 28, 2012 at 3:47 PM, Jov wrote:
>
>
> 2012/12/28 wd
>
>> hi,
>>
>> wd_test=# \d t1
>> Table "public.t1"
>&
33 matches
Mail list logo
