it copied before leaving ?
In other words, when I want to switchover, is it sufficient to stop
postgresql,
and rsync the last partial WAL (the last modified one), or do I have to
check if
every WAL file is in sync before starting the other server ??
Thank you in advance,
Philipp
her server ??
Thank you in advance,
Philippe Ferreira
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
"sequence_name"...
Any idea ?
Thank you in advance,
Philippe Ferreira, France.
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
tion "seq_min" line 4 at execute statement
So, it seems that it is impossible to lock a sequence !
If it is the case, how can I achieve the same result without locking the
sequence ?
Thank you again,
Philippe Ferreira.
---(end of broadcast)-
END LOOP;
END LOOP;
RETURN;
END;
$$ LANGUAGE plpgsql;
-
It gives the result I expect (and it doesn't interfere with concurrent
uses of the sequence), but it is not very optimized !
So, if someone hav
using this sequence would then break !!
The only solution I found to prevent this is with my "loops" !!
Best regards,
Philippe Ferreira.
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
o the database they belong :
hostsamegroup all 0.0.0.0 0.0.0.0 md5
Bye,
Philippe Ferreira.
Hi all,
I have a faint memory of it being possible to create users
"inside" *one* given database by way of a particular "create
user" syntax along the line
So, in this example, if I don't increment the last value of my
sequence from 1011 to 1013 (before my last "SWITCHOVER"), it
will output "1012A" (instead of 1014A), and my new record will
conflict with an existing one !!
Thank you for your interest,
Philippe Ferrei
l.org/pgsql-hackers/2001-10/msg00928.php
Best regards,
Philippe Ferreira.
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
f PostgreSQL : 8.0.4)
Thank you,
Philippe Ferreira.
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
do switchover. In this case, I
think that nothing
should change...
But, I recognize that using PITR for switchover is rather an
"unsupported" functionnality...
Thank you,
Philippe Ferreira.
---(end of broadcast)---
TIP 6: explain analyze is your friend
To get "exact" restart behavior we'd need to emit a separate xlog
record for each nextval() command, which seems like a pretty high
price considering that you cannot assume no holes in the sequence
values anyway.
Hi,
Why not give the choice at compile-time ?
Philippe.
Thank you in advance,
Philippe Ferreira.
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
y sources.
Try
SELECT * FROM mytable WHERE myreal >= 10.49 AND myreal <= 10.51;
and see what result that gives.
This way, it works...
Philippe Ferreira.
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desi
Hi,
I've just realized that this way, it works very fine :
SELECT * FROM mytable WHERE myreal = 13.95::real;
But I still don't understand very well why I need the explicit
conversion (::real) ...
Philippe Ferreira.
---(end of
Hi,
Thank you all for your comments.
Finally, I think I will simply use the data type NUMERIC instead of REAL
in all my columns !!
This type is more appropriate to store prices !
Philippe Ferreira.
Try this:
SELECT 13.95 = 13.95::real;
It should yield false, because the first number
tual pg_hba.conf file is ideal !
If we would have to start the database in order to reconfigure it to
prevent normal connections, a normal user could take advantage of this
to connect during this process !!
Don't loose flexibility and security for some "elegant&q
of the current WAL every 5 minutes...
Will the wal file copied usefull in those situations?
Of course, yes !
The filled WAL files (WAL archives) are automatically copied by the
postmaster process,
but you need to copy yourself the current one to be able to recover the
last stuff !
What other
"pgdump" of both databases, and use the "diff" tool to compare the
two generated files !
(But I hope your databases are not too big...)
Philippe Ferreira.
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will i
ideal.
I am running Postgresql v 8.0 on Windows XP.
Hi,
If you need a GUI to manage your Postgresql databases, you have "PgAdmin"...
Philippe Ferreira.
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Thanks I am using pgadmin for development. I'm looking for a tool with
which I can develop an interface that will be used for entering and
accessing information in context with the user tasks.
Bob
Hi,
Why not OpenOffice "Base" ?
http://www.openoffice.org/product/base
Yeah, LISTEN/NOTIFY is definitely a lighter-weight solution--I didn't
think of that before.
Hi,
I'm interested too in using this method !
Can anyone give a simple example of how to use/implement it ?
Or good links to clear/quick documentation about these functions ?
Thank you
Hi,
If the downtime is a concern, you could use Slony-1 for the migration.
Philippe Ferreira.
[EMAIL PROTECTED] napisał(a):
Could anybody point to an on-line resource about the steps involved with
upgrading of PostgreSQL 8.x on a production FreeBSD 5.4 with minimum
downtime (i.e. 1 - stop
23 matches
Mail list logo
