I get the same "weird" errors (WAL file is from different database system)
too with Ubuntu and Postgresql 9.3 when setting up a slave using rsync.
1. I installed postgresql on the slave (which automatically does the
initdb):
sudo apt-get install postgresql-9.3
2. Modified my postgresql.conf fi
On Fri, Aug 9, 2013 at 9:54 AM, Quentin Hartman
wrote:
> OK, figured this out. I had it start copying the pg_xlog directory as well
> when doing the initial sync. I realized this is also the first time I've
> setup replication from scratch using 9.2. All my other 9.2 pairs were setup
> on either 9
On Fri, Aug 9, 2013 at 8:33 AM, Quentin Hartman
wrote:
> This pair of servers aren't replacing anything, they are new, empty servers.
That should be 'empty server', singular.
> Before starting the slave at all, I'm copying the entire data filestructure
> over to it via rsync. I'm doing almost ex
OK, figured this out. I had it start copying the pg_xlog directory as well
when doing the initial sync. I realized this is also the first time I've
setup replication from scratch using 9.2. All my other 9.2 pairs were setup
on either 9.0 or 9.1, and have been upgraded from there with replication
al
This pair of servers aren't replacing anything, they are new, empty
servers. Before starting the slave at all, I'm copying the entire data
filestructure over to it via rsync. I'm doing almost exactly what is
described here:
http://wiki.postgresql.org/wiki/Binary_Replication_Tutorial#Binary_Replicat
On Fri, Aug 9, 2013 at 8:55 AM, Quentin Hartman
wrote:
> 2013-08-08 23:47:30 GMT LOG: WAL file is from different database system
> 2013-08-08 23:47:30 GMT DETAIL: WAL file database system identifier is
> 5909892614333033983, pg_control database system identifier is
> 5909892824786287231.
It look
I'm going through all my usual steps for setting up streaming replication
on a new pair of servers. Modify configs as appropriate, rsync data from
master to slave, etc. I have this all automated with chef, and it has been
pretty bulletproof for awhile. However, today, I ran into this when
starting
Hi all.
I've got this error message while running an SQL function:
BEGIN
psql:filtb.sql:1029: ERROR: COMMIT is not allowed in a SQL function
CONTEXT: SQL function "f_relazione" during startup
funzione SQL "f_relazione" istruzione 1
END
Of course, I have no COMMIT command either in t
On Monday 16 July 2007 12:18:23 Richard Huxton wrote:
> Vincenzo Romano wrote:
> > Hi all.
> >
> > I've got this error message while running an SQL function:
> >
> > BEGIN
> > psql:filtb.sql:1029: ERROR: COMMIT is not allowed in a SQL
> > function CONTEXT: SQL function "f_relazione" during s
Vincenzo Romano wrote:
Hi all.
I've got this error message while running an SQL function:
BEGIN
psql:filtb.sql:1029: ERROR: COMMIT is not allowed in a SQL function
CONTEXT: SQL function "f_relazione" during startup
funzione SQL "f_relazione" istruzione 1
END
Of course, I have no C
Hi all.
I've got this error message while running an SQL function:
BEGIN
psql:filtb.sql:1029: ERROR: COMMIT is not allowed in a SQL function
CONTEXT: SQL function "f_relazione" during startup
funzione SQL "f_relazione" istruzione 1
END
Of course, I have no COMMIT command either in t
Hi Tom,
We actually have plenty of storage free. Our database server is
connected to an Xserve RAID.
Filesystem Size Used Avail Capacity Mounted on
/dev/disk1s3745G21G 725G 3%/Volumes/nitro1.1
/dev/disk2s3745G 4.1G 741G 1%/Volumes/nitro1.2
We store the
Brendan Duddridge <[EMAIL PROTECTED]> writes:
> Next exception:SQL State:XX000 -- error code: 0 -- msg: ERROR:
> could not read from hash-join temporary file: Unknown error: 0
> Any one know what that could mean?
It seems to imply unexpected end-of-file while reading from a temp file
... u
Hi,Today we received a very odd error from our PostgreSQL database:"update category_product set product_is_active = p.is_active, product_status_code = p.status_code from product p where category_product.product_id = p.product_id and category_id = 1001415;">: Next exception:SQL State:XX000 -- er
Hi,
I have installed previous version of postgresql. 8.x. I uninstalled it.
Then remove the superuser in My Computer ( right click ) --> Properties
--> in tab Advanced --> Settings button. I try to install postgresql
8.0.1. In service configuration, I checked the install as service
checkbox. Fille
On Wed, Jun 27, 2001 at 11:30:54AM -0400, Tom Lane wrote:
: Philip Molter <[EMAIL PROTECTED]> writes:
: > I am using 7.1.2.
:
: Don't suppose you want to dig in there with a debugger when it happens?
: You must be seeing some hard-to-replicate problem in VACUUM's
: tuple-chain-moving logic. That
Philip Molter <[EMAIL PROTECTED]> writes:
> I am using 7.1.2.
Drat.
Don't suppose you want to dig in there with a debugger when it happens?
You must be seeing some hard-to-replicate problem in VACUUM's
tuple-chain-moving logic. That stuff is pretty hairy, and I doubt
anyone will be able to intu
17 matches
Mail list logo
