. Granted their cheap replication software costs more then
you paid for that server that is running MySQL, and the expensive
replication probably costs more then a cabinet worth of MySQL
servers. :-)
--
Kevin Barnard
kevin.barn...@laser2mail.com
--
Sent via pgsql-general mailing list
are in child tables? I can think of a few migration ideas
doing this.
Thanks in advance.
--
Kevin Barnard
kevin.barn...@laser2mail.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
I've just upgraded a 7.4 install to 8.0.3 and we've suddenly run into
lock issues that were not present in 7.4. I'm look for help on
this matter, because I'm a little confused. Downgrading is really
not an option at this point, we really really need the 8.0
features on the DB and a dump/restore
I know I've seen this message before but I'm not quite sure what it
means. I think it's because I have two vacuums running over each
other. Does this sound right? It's comming from 7.4.x server.
ERROR: tuple concurrently updated
---(end of
On Thu, 11 Nov 2004 13:56:48 -0500, Tom Lane [EMAIL PROTECTED] wrote:
Were they both VACUUM ANALYZEs? There's a known gotcha that if you
ANALYZE the same table concurrently in two different sessions, one
of them can fail this way when it goes to update the pg_statistic
entries. (Harmless,
Currently the mailing list is also hosted in a newsgroup at
new.postgresql.org. The news group is not Official so it is not
carried by all news servers. There are some users who can not
participate in a mailing list comfortably for one reason or another.
Some of these individuals would like
FUCK THAT ASSHOLE MIKE COX! HE loves SUCKING COCK!!!
Kevin Barnard
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
I am generally interested in a good solution for this. So far our
solution has been to increase the hardware to the point of allowing
800 connections to the DB.
I don't have the mod loaded for Apache, but we haven't had too many
problems there. The site is split pretty good between dynamic and
OS 10.3 IMHO is more stable then 10.2. I haven't us OS X in a
production environment only for development. I have yet to have any
problems with it crashing.
I haven't really run any tests to load it down but that's only because
I never expect to use in production. We have far too many IBM
You have a conceptual error. When connecting you are connecting to a
database. With out the database you are not connecting to anything
hence the failure.
Typically to do what you are trying to do you would connect to the
database template1 unless a database is specified. If you have
another
This sounds like a WAL segment recycling issue. I believe 8.0 should
relieve some of the stress. I've had this problem before and found
that increasing the number of check point segments has helped a
little. You still get the a wallop when this happens, increasing the
size should make that
On Tue, 26 Oct 2004 17:05:27 -0700, Robby Russell [EMAIL PROTECTED] wrote:
On Tue, 2004-10-26 at 17:26 -0400, Mike Mascari wrote:
joking
Apparently gamma functions and string theory have little to do with
understanding the relational model of data.
/joking
m.. string theory.
On Fri, 22 Oct 2004 14:18:52 -0400, Jan Wieck [EMAIL PROTECTED] wrote:
That multiple hosts sounds that he came across the NDB cluster stuff
that will become available in MySQL someday. Be aware that this new
table handler will to my knowledge NOT support foreign keys. So the
enforcement of
PostgreSQL uses it's own internal storage engine. It doesn not
support multiple one. As for splitting files accross partitions this
is a feature of version 8.0 called tablespaces.
http://developer.postgresql.org/docs/postgres/manage-ag-tablespaces.html
Should get you pointed in the right
A better solution is to use the serial data type. OID is depreciated
and may go away.
http://www.postgresql.org/docs/7.4/static/datatype.html#DATATYPE-SERIAL
On 19 Oct 2004 07:54:36 -0700, Raffaele Spizzuoco
[EMAIL PROTECTED] wrote:
Hi!
I'm from Italy, and sorry about my english...
I have
Why not do this on the client side? I'm just curious as to the benfit
of doing this on the server.
On Tue, 19 Oct 2004 11:10:58 -0500, Hicham G. Elmongui
[EMAIL PROTECTED] wrote:
I need to select all tuples from a table, but need them to be fetched with a
constant delay (say 1 sec) between
Have you looked at the 7.3 configuration file vs. the 8.0. It's
possible that the 7.3 file is tweakled better then the 8.0. Have you
anaylzed the tables after loading the data into 8.0
On Thu, 14 Oct 2004 12:01:38 -0500, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hi,
We are experiencing
There might be a better way then this but this works
SELECT a, a+1 as b from (SELECT 1+1 as a) as ab;
On 16 Oct 2004 11:18:48 -0700, ryan [EMAIL PROTECTED] wrote:
Hello,
Is there any way to reuse a column label in a select list like this:
SELECT 1 + 1 AS a, a + 1 AS b;
I vaguely
SELECT trim(leading '0' from to_char(now(), 'HH:MM AM'))
I think is what you really want. This gets rid of the nasty leasing 0.
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
Going back to the documents I think Tom's answer of prepending FM is
better then mine.Look at table 9-22 for other options
On Tue, 5 Oct 2004 10:06:51 -0500, Todd P Marek [EMAIL PROTECTED] wrote:
On Oct 5, 2004, at 10:00 AM, Kevin Barnard wrote:
SELECT trim(leading '0' from
Apache/PHP are already prebuilt on Mac OS X. All you need to do is
donwload the postgres tarball config and compile.
Small notte on the compile. When you compile postgres either turn off
readline support or download readline from GNU and compile the static
lib.
I don't remember off hand but I
Maybe this is a server vs normal OS X issue. I am postgres on a
normal iMac 10.3.5 with no problems, but this is just a developent box
so I don't need the server version. All of the servers that I run are
Linux/FreeBSD. I don't have access to a Mac server, if I did I would
test this myself.
Use the return type of SETOF and user the RETURN NEXT for each record.
If you are already returning a record that's half the battle.
http://www.postgresql.org/docs/7.4/static/plpgsql-control-structures.html#PLPGSQL-STATEMENTS-RETURNING
On Thu, 23 Sep 2004 11:26:15 -0400, Robert Fitzpatrick
UPDATE related_products SET related_counter = related_counter
WHERE .
only updates if the record exists
INSERT (x,y,z) SELECT ?,?,1 WHERE NOT EXISTS (SELECT 1 FROM
related_products WHERE .)
Inserts if the key does not exist.
On Sat, 11 Sep 2004 00:02:26 +0200, Gaetano Mendola [EMAIL
24 matches
Mail list logo
