Hello Everyone
My employer is evaluating PostgreSQL as a possible replacement for Oracle 11g
R2 and MS-SQL 2008 R2 for some systems.
I am completely new to PostgreSQL but experienced in MS-SQL and also in Oracle
11g R2.
We need to establish what PostgreSQL is good at and not so good at - so we c
thank you it's helpfull
On Fri, May 8, 2015 at 7:43 PM, Adrian Klaver
wrote:
> On 05/08/2015 01:56 AM, Ramesh T wrote:
>
>> Hi All,
>>I want move functions from onedatabase to other database in same host
>> on windows 7 and installed postgres version is 9.4.I'm using pgadmin3
>> tool.
>> an
Sachin Srivastava wrote:
> Could you help us solving the below error which we are getting during taking
> pg_dump.
>
> pg_dump: SQL command failed
>
> pg_dump: Error message from server: ERROR: invalid page header in block
> 14521215 of relation
> pg_tblspc/18140340/PG_9.1_201105231/18140346/
Hi,
On 05/07/15 05:49, Sachin Srivastava wrote:
Dear Concner,
Could you help us solving the below error which we are getting during
taking pg_dump.
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: invalid page header in block
14521215 of relation pg_tblspc/18140340/PG_
On 05/08/2015 01:56 AM, Ramesh T wrote:
Hi All,
I want move functions from onedatabase to other database in same host
on windows 7 and installed postgres version is 9.4.I'm using pgadmin3 tool.
any help..?
Two options with pgAdmin:
1) See here
http://www.pgadmin.org/docs/1.20/backup.html
Hi All,
I want move functions from onedatabase to other database in same host on
windows 7 and installed postgres version is 9.4.I'm using pgadmin3 tool.
any help..?
Dear Concner,
Could you help us solving the below error which we are getting during taking
pg_dump.
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: invalid page header in block
14521215 of relation pg_tblspc/18140340/PG_9.1_201105231/18140346/18140757
pg_dump: The comma
OK I think I have a solution, using the following script as the
restore_command
echo $1 | grep history > /dev/null
if [ $? -eq 0 ]; then
exit 1
fi
scp postgres@postgres3:/archived_wals/$1 $2
This seems to work, as it restricts slave servers from switching timeline
from the archive by
