I actually just wanted to know if there is a way around this problem.
Obviously it is implemented that way for whatever reason.
I still though think some arguments given in some of the replies, while
probably correct, are besides the point.
Sorry. I was hoping someone else would answer.
I use a
On Jan 20, 2005, at 16:03, David Garamond wrote:
Dann Corbit wrote:
True, but the standard says nothing about the creation of an index, so
you can make it behave in any way that you see fit.
But I thought we are talking about unique _constraint_ here (which is
certainly regulated by the standard).
Hi,
Am Mittwoch, den 19.01.2005, 15:02 -0800 schrieb J. Greenlees:
> Roman Neuhauser wrote:
> > # [EMAIL PROTECTED] / 2005-01-20 01:35:32 +1100:
> >
> >>i have a unique index on a table over multiple columns. If now one of
> >>the records has a null value in one of the indexed columns i can inse
I think I see what was happening. I was looking at the output of the
SELECT that is used for opening a cursor. Got it. Thanks for your help.
It's kind of a meta-select in the printed version of a plan if the
cursor being opened is a SELECT.
-tfo
--
Thomas F. O'Connell
Co-Founder, Information Ar
Dann Corbit wrote:
True, but the standard says nothing about the creation of an index, so
you can make it behave in any way that you see fit.
But I thought we are talking about unique _constraint_ here (which is
certainly regulated by the standard).
--
dave
---(end of broa
Alex <[EMAIL PROTECTED]> writes:
> I actually just wanted to know if there is a way around this problem.
> Obviously
> it is implemented that way for whatever reason.
The way around is to make all the columns NOT NULL. For most applications
unique indexes don't make much sense on nullable column
Hello,
I am an Oracle DBA and I want do a Postgresql ‘proof
of concept’ at the large corporation where I work to test the benefits of
using Postgresql in our environment. I want to install Postgresql onto a “production”
server that currently runs Oracle. Are there any problems with runnin
I'm still having problems to restore a database.
The dump command used was:
# pg_dump -Ft -b -o database > database.dump
This dump was created in Postgres 8.0beta5 (Windows).
When I try to restore this file in Postgres 8.0-rc3 (Linux) I get this
error:
# pg_restore -Ft -d database database.dum
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> I recall this being discussed before, but I couldn't manage to find it
> in the archives.
>
> Is there any way to see how many rows a running transaction has written?
> vacuum analyze verbose only reports visible rows.
Not AFAIK. In the past I've done
Tom Lane <[EMAIL PROTECTED]> writes:
> "Dann Corbit" <[EMAIL PROTECTED]> writes:
>
> > Even at that, I think that being able to insert more than one null value
> > into a unique index should be considered as a bug (or diagnosed as an
> > error).
>
> Direct your complaints to the ISO SQL standard
I actually just wanted to know if there is a way around this problem.
Obviously it is implemented that way for whatever reason.
I still though think some arguments given in some of the replies, while
probably correct, are besides the point.
I use a unique index that may contain null values. On
I recall this being discussed before, but I couldn't manage to find it
in the archives.
Is there any way to see how many rows a running transaction has written?
vacuum analyze verbose only reports visible rows.
--
Jim C. Nasby, Database Consultant [EMAIL PROTECTED]
Give your comput
On Wed, 19 Jan 2005, Stephan Szabo wrote:
>
> On Wed, 19 Jan 2005, Dann Corbit wrote:
>
> > True, but the standard says nothing about the creation of an index, so
> > you can make it behave in any way that you see fit.
>
> The unique index is however used to model the unique constraint in
> Postgr
On Wed, 19 Jan 2005, Dann Corbit wrote:
> True, but the standard says nothing about the creation of an index, so
> you can make it behave in any way that you see fit.
The unique index is however used to model the unique constraint in
PostgreSQL which I had thought was clear from my statement so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Although with your very little load a manual or cron based vacuum full once a
week will be more than enough.
I'm doing a biweekly vacuum full with one of my customer's machines (an
office application that uses pg as backend) and never had complaint
"Vladimir S. Petukhov" <[EMAIL PROTECTED]> writes:
> select * from nets;
> name | note | net
> --+--+---
> | | 172.16.0.0/16
> (1 row)
> select * from nets where net >>= '172.16.4.0/8';
> name | note | net
> --+--+-
> (0 rows)
Are you confusing >>
Sorry, of course... :)
On Thursday 20 January 2005 03:15, Vladimir S. Petukhov wrote:
> select * from nets;
>
> name | note | net
> --+--+---
>
> | | 172.16.0.0/16
>
> (1 row)
>
> select * from nets where net >>= '172.16.4.0/8';
> name | note | net
> --+---
On Wed, 19 Jan 2005, Dann Corbit wrote:
> Even at that, I think that being able to insert more than one null value
> into a unique index should be considered as a bug (or diagnosed as an
> error).
AFAICT the UNIQUE constraint that it's used to model explicitly allows
multiple NULLs in the spec s
The ISO SQL Standard does not even define an index, and so any index is
an extension to the standard (though primary keys and foreign keys imply
them).
At least in the SQL Standard that I have (ANSI/ISO/IEC 9075-1-1999 and
related documents) has no definition of an index. Perhaps the newer
versio
True, but the standard says nothing about the creation of an index, so
you can make it behave in any way that you see fit.
-Original Message-
From: Stephan Szabo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 19, 2005 4:27 PM
To: Dann Corbit
Cc: [EMAIL PROTECTED]; J. Greenlees; pgsql-
select * from nets;
name | note | net
--+--+---
| | 172.16.0.0/16
(1 row)
select * from nets where net >>= '172.16.4.0/8';
name | note | net
--+--+-
(0 rows)
??
---(end of broadcast)---
TIP 1:
"Dann Corbit" <[EMAIL PROTECTED]> writes:
> Or (perhaps better yet, violating trichotomy) ...
> If has a null numeric value, then ALL of the following are
> FALSE for that case:
> Some_column < 0
> Some_column > 0
> Some_column = 0
> Some_column <> 0 // This is the one that many find surprising
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Why not write a function that converts the LOC number to an integer,
such that sorting on those integers will sort the numbers correctly?
Apparently you can even build an index on this type of function now, to
accelerate the sort.
cvt_loc(TEXT) ->
Opps... resending to list as well. Perhaps someone can add more insight below.
And check the documentation at
http://borg.postgresql.org/docs/8.0/interactive/extend.html .
-- Forwarded message --
From: Mike Rylander <[EMAIL PROTECTED]>
Date: Thu, 20 Jan 2005 00:05:40 +
Subje
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Uh, does the Python doc specify "platform" line endings, or "normal
(\n)" line endings? It sounded to me like it always wanted the
UNIX-style \n line endings, so that using those would result in
portability...
On Jan 19, 2005, at 6:03 PM, Alvaro He
Null values are a big surprise to almost every end-user (though the
programmers are OK with them).
Look at the astonishment on the face of your end user when you tell them
that:
SELECT COUNT(*) FROM clothing WHERE clothing_color = 'green'
+
SELECT COUNT(*) FROM clothing WHERE NOT clothing_color =
Yes, autovacuum is better.
I am a fossil from 7.1.3 days.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 19, 2005 2:10 PM
To: Dann Corbit
Cc: pgsql-general@postgresql.org; [EMAIL PROTECTED];
Mark
Subject: Re: [GENERAL] need an advice on runn
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-general-
> [EMAIL PROTECTED] On Behalf Of Mike Rylander
> Sent: Wednesday, January 19, 2005 6:10 PM
> To: Rick Schumeyer; PgSql General
> Subject: Re: [GENERAL] sorting library of congress numbers
>
> On Wed, 19 Jan 2005 17:37:20
According to Date you should never use NULLs. This is because a NULL can
mean many different things. It can mean not known (e.g. I know he has an
age but I don't know what it is), It can be not applicable (e.g. in a
Party table of organizations and people, people would be of a certain sex
but an or
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-general-
> [EMAIL PROTECTED] On Behalf Of Scott Marlowe
> Sent: Wednesday, January 19, 2005 5:54 PM
> To: Rick Schumeyer
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] sorting library of congress numbers
>
> On Wed,
On Wed, 19 Jan 2005 17:37:20 -0500, Rick Schumeyer <[EMAIL PROTECTED]> wrote:
>
> I have a table where one of the columns is a library of congress number.
>
> I would like to be able to ORDER BY this column.
>
First off, by LOC numbers do you mean Title Control Numbers like
"o00325992" or "i0
On Thu, Jan 20, 2005 at 09:50:43AM +1100, Stuart Bishop wrote:
> Martijn van Oosterhout wrote:
> > User defined functions using the Python language must use the newline
> > delimiter of the server OS. There is currently no standard way of
> > determining the newline delimiter of the server. Not
Roman Neuhauser wrote:
# [EMAIL PROTECTED] / 2005-01-20 01:35:32 +1100:
i have a unique index on a table over multiple columns. If now one of
the records has a null value in one of the indexed columns i can insert
the same record multiple times.
Is this a problem within postgres or expected?
Martijn van Oosterhout wrote:
On Wed, Jan 19, 2005 at 06:28:25PM +1100, Stuart Bishop wrote:
Michael Fuhr wrote:
If Python's behavior is intentional then the newline burden would
seem to be on the user or on plpythonu. I think Tom's point is
that that's just silly
Changing this behavior in Pyt
On Wed, 2005-01-19 at 16:37, Rick Schumeyer wrote:
> I have a table where one of the columns is a library of congress
> number.
>
> I would like to be able to ORDER BY this column.
>
>
>
> Currently, the column is a varchar. Unfortunately, a normal string
> comparison
>
> will not work.
>
>
I have a table where one of the columns is a library of
congress number.
I would like to be able to ORDER BY this column.
Currently, the column is a varchar. Unfortunately, a
normal string comparison
will not work.
First, has anyone done this already?
If not, I’m thinking I w
> The load will increase in the near future: insert/update/delete
> activity will be at least one in 5 minutes.
>
> What maintenance should I need to do?
You should make sure PostgreSQL is properly tuned for your
hardware and you should run vacuum, say, daily or so.
Karsten
--
GPG key ID E407134
Hi all,
In working through some problems with rows and variables, I
installed PL/TCL into my Postgres 8.0 installation on Windows XP.
Unfortunately, when I try to run any PL/TCL functions, I get the response:
ERROR: could not create "normal" interpreter
I have ActiveTCL 8.4.9 installed,
Do you not recommend autovacuum?
Rick
"Dann Corbit"
Once per day dump database to disk.
Once per day do a vacuum full.
That should be plenty.
Since there are 1440 minutes per day, you are only looking at 288
transactions per day. Not exactly a taxing transaction load.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
On Wed, 2005-01-19 at 11:24 -0800, [EMAIL PROTECTED] wrote:
> [non-word character being ignored by ORDER BY]
...
> testdb1=> show LC_COLLATE;
> lc_collate
> -
> en_US.UTF-8
> (1 row)
this is a 'feature' of your en_US locale:
bash$ export LC_COLLATE=en_US
bash$ (echo "usra";echo "usr
On Wed, 19 Jan 2005 18:51:40 +0100, pginfo <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I just installed pg 8.0 on freeBSD 5.3.
>
> All is ok, but if I try to increase max_connections to 256 (or more) pg
> do not starts.
>
> Yes, I readet the docs and I know that I need to increase shared memory
>
On Wed, Jan 19, 2005 at 07:39:29AM -0700, Michael Garriss wrote:
> We had a significant production outage with a box running 8.0 Beta 4,
> 140GB data, 190GB index. We think it was a bad RAID controller card.
> Our transaction logs are gone but we have raw data.
>
> How can we recover this data
Hi,
I have a small data base ~ 10 tables. each table get
insert/update/delete few times a day. postgresql is running for a
month.
The load will increase in the near future: insert/update/delete
activity will be at least one in 5 minutes.
What maintenance should I need to do?
Thanks,
Mark.
Bruno Lavoie wrote:
> is there a way to easily configure postgresql to auth with pam on
> debian?
Yes, the same way as on any other platform. What particular problem are
you having?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)-
On Wed, 19 Jan 2005 21:39:23 +0200 (EET), Devrim GUNDUZ
<[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> On Wed, 19 Jan 2005, Guy Rouillier wrote:
>
> >> On whitebox & RHEL ext3 is really the only choice. However, FC3
> >> provides all the other major fil
Hello,
is there a way to easily configure postgresql to auth with pam on debian?
thanx a lot!
Bruno
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Wed, 19 Jan 2005, Guy Rouillier wrote:
On whitebox & RHEL ext3 is really the only choice. However, FC3
provides all the other major filesystems as choices (XFS, reiser).
I just tried to install FC3 AMD64, and the only choice it would give me
for
Guy Rouillier wrote:
Lonni J Friedman wrote:
On whitebox & RHEL ext3 is really the only choice. However, FC3
provides all the other major filesystems as choices (XFS, reiser).
I just tried to install FC3 AMD64, and the only choice it would give me
for an installation was ext3. Since I pr
Hooray! Thank you to all responsible for and involved in this great
release! This database truly rocks!
:)
-Original Message-
From: Marc G. Fournier [mailto:[EMAIL PROTECTED]
Sent: January 19, 2005 6:03 AM
To: pgsql-announce@postgresql.org
Cc: pgsql-general@postgresql.org
Subject: P
Lonni J Friedman wrote:
>
> On whitebox & RHEL ext3 is really the only choice. However, FC3
> provides all the other major filesystems as choices (XFS, reiser).
I just tried to install FC3 AMD64, and the only choice it would give me
for an installation was ext3. Since I prefer Reiser, I gave u
I am seeing some unexpected results for an ORDER BY in a query. It looks
to me as if the sorting is confused about how to handle the slash or
backslash character in a string. It acts as if ignoring it. Here is a
sample:
Table "public.test_table"
Column | Type | Mo
Hi all,
I just installed pg 8.0 on freeBSD 5.3.
All is ok, but if I try to increase max_connections to 256 (or more) pg
do not starts.
Yes, I readet the docs and I know that I need to increase shared memory
and semaphores.
I recompile my kernel and set :
options SYSVSHM
options
The website went down long before the news was posted to slashdot. By
the time it hit slashdot, things were fixed already. Luckily.
//Magnus
> http://en.wikipedia.org/wiki/Slashdot_effect
>
>
> On Wed, 2005-01-19 at 10:06, [EMAIL PROTECTED] wrote:
> > What does that mean?
> >
> >
> >
> "Bruno" == Bruno Wolff <[EMAIL PROTECTED]> writes:
Bruno> http://en.wikipedia.org/wiki/Slashdot_effect
Except that wikipedia itself is suffering from the Slashdot effect
right now. :)
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
http://www.stonehenge.com
On Wed, 19 Jan 2005 09:19:33 -0800, Bricklen Anderson
<[EMAIL PROTECTED]> wrote:
> Joshua D. Drake wrote:
> > Martijn van Oosterhout wrote:
> >
> >> No difference whatsoever from PostgreSQL's point of view. Use whichever
> >> distribution is easiest for you to administer. After all, there's no
> >>
On Wed, Jan 19, 2005 at 11:06:56 -0500,
[EMAIL PROTECTED] wrote:
> What does that mean?
http://en.wikipedia.org/wiki/Slashdot_effect
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
http://en.wikipedia.org/wiki/Slashdot_effect
On Wed, 2005-01-19 at 10:06, [EMAIL PROTECTED] wrote:
> What does that mean?
>
>
>
>
>
Sincerely,
Joshua D. Drake
Out of curiousity, which fs would you recommend for a ~terabyte oltp db?
XFS without a doubt. XFS has excellent large file (and filesystem) support.
I second the XFS statement.
Sincerely,
Joshua D. Drake
--
Command Prompt, Inc., home of Mammoth Postg
On Wed, 19 Jan 2005 09:03:31 -0800, Joshua D. Drake
<[EMAIL PROTECTED]> wrote:
> Martijn van Oosterhout wrote:
>
> >No difference whatsoever from PostgreSQL's point of view. Use whichever
> >distribution is easiest for you to administer. After all, there's no
> >point installing Postgres on a mach
When I had customers faced with this decision, we made the
recommendation based on which distro employs major contributors
of the software project in question.
For Postgresql's case, RedHat's employment of Tom made
our recommendation to use Red Hat.
Some of our clients are running .NET front ends,
Michael Meskes wrote the following on 19.01.2005 11:16:
I would be happy to help debugging this. But up to now I didn't even
know about this problem. Could you please send me a test case so I can
reproduce this?
It is from a very large production example. I have to work a bit to trim
this down t
Nefnifi, Kasem wrote:
Dear,
I'm new in pgsql, come from oracle and sql server.
any one can help by transferring a pl/sql procedure that imports data from a flat file, using UTL_FILE, and inserts or updates tables.
bellow the proc:
You can't do this from pl/PgSQL. You will need to use plPerl,
plP
Joshua D. Drake wrote:
Martijn van Oosterhout wrote:
No difference whatsoever from PostgreSQL's point of view. Use whichever
distribution is easiest for you to administer. After all, there's no
point installing Postgres on a machine you don't know how to maintain
or tune :)
Actually there is a d
http://it.slashdot.org/article.pl?sid=05/01/19/1312224&tid=221&tid=198&tid=185
On Wed, 19 Jan 2005 11:06:56 -0500, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> What does that mean?
>
> Lonni J Friedman
> <[EMAIL PROTECTED]> To:
> pgs
What does that mean?
Lonni J Friedman
Martijn van Oosterhout wrote:
No difference whatsoever from PostgreSQL's point of view. Use whichever
distribution is easiest for you to administer. After all, there's no
point installing Postgres on a machine you don't know how to maintain
or tune :)
Actually there is a difference from PostgreS
You should look www.linuxiso.org.
There you may find the ISO of a great variety of distros.
C ya,
Bruno Almeida do Lago
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Geoffrey
Sent: Wednesday, January 19, 2005 1:01 PM
To: pgsql-general@postgresql.org
On Wed, Jan 19, 2005 at 09:26:11AM -0500, Eric E wrote:
> I belive I came across a message that indicated that you could do
> such a thing in TCL. Do you know if this is true? Can TCL in 7.4.2
> get a field from a rowtype varaible like this?
See the PL/Tcl trigger documentation -- it has an exa
# [EMAIL PROTECTED] / 2005-01-20 01:35:32 +1100:
> i have a unique index on a table over multiple columns. If now one of
> the records has a null value in one of the indexed columns i can insert
> the same record multiple times.
>
> Is this a problem within postgres or expected?
In SQL, NUL
Great! Thank you guys.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Marc G. Fournier
Sent: Wednesday, January 19, 2005 2:03 PM
To: pgsql-announce@postgresql.org
Cc: pgsql-general@postgresql.org
Subject: [GENERAL] PostgreSQL 8.0.0 Released
After more t
* Omar Kilani <[EMAIL PROTECTED]> [0146 15:46]:
> Hi,
>
> If your font issues are still occuring after doing a Ctrl-Reload (and
> switching back to 'Normal' text), then, can you please send me a screenshot?
Sorted now, thanks. Didn't need to shift-relod, it just worked...
--
'zzz..Kill all hum
Devrim GUNDUZ wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Sat, 8 Jan 2005, Esteban Kemp wrote:
I'm starting to develop a production enviroment with Postgres and
Tomcat, And I have to choose between some free linux distribution like:
whitebox
RHEL
RHEL is not free (of charge).
Fed
Dear,
I'm new in pgsql, come from oracle and sql server.
any one can help by transferring a pl/sql procedure that imports data from a
flat file, using UTL_FILE, and inserts or updates tables.
bellow the proc:
CREATE OR REPLACE Procedure UPD is
sOracleMsg varchar2(512);
sCusto
# [EMAIL PROTECTED] / 2005-01-19 14:57:47 +0100:
> I have a rule similar to this:
>
> CREATE RULE rule_branch_delete AS
> ON DELETE TO tree
> DO DELETE
> FROM tree
> WHERE ancestor_id IS NOT NULL
> AND OLD.child_id = ancestor_id;
> If I try a delete on the tree table I get "Infinit
On Thu, 20 Jan 2005, Alex wrote:
> i have a unique index on a table over multiple columns. If now one of
> the records has a null value in one of the indexed columns i can insert
> the same record multiple times.
>
> Is this a problem within postgres or expected?
Expected. NULLs are effectively
We had a significant production outage with a box running 8.0 Beta 4,
140GB data, 190GB index. We think it was a bad RAID controller card.
Our transaction logs are gone but we have raw data.
How can we recover this data? Can the transaction logs be reset? Can
we safely set this zero_damaged
On Wed, Jan 19, 2005 at 02:57:47PM +0100, Alban Hertroys wrote:
> I have a rule similar to this:
>
> CREATE RULE rule_branch_delete AS
> ON DELETE TO tree
> DO DELETE
> FROM tree
> WHERE ancestor_id IS NOT NULL
> AND OLD.child_id = ancestor_id;
> If I try a delete on the tree tab
On Wed, 2005-01-19 at 09:02 -0400, Marc G. Fournier wrote:
> After more than a year of hard work, the PostgreSQL Global Development
> Group proudly announces the release of version 8.0.0 of the PostgreSQL
> ORDBMS. This release involves possibly more major changes than any prior
> version of P
Hi,
i have a unique index on a table over multiple columns. If now one of
the records has a null value in one of the indexed columns i can insert
the same record multiple times.
Is this a problem within postgres or expected?
Example:
index unique, btree (colA, colB, colC);
would still allow me t
No difference whatsoever from PostgreSQL's point of view. Use whichever
distribution is easiest for you to administer. After all, there's no
point installing Postgres on a machine you don't know how to maintain
or tune :)
Hope this helps,
On Sat, Jan 08, 2005 at 11:14:00AM -0300, Esteban Kemp wro
Martijn van Oosterhout wrote:
Sorry, RULEs are like macros, they essentially expand and transform
your original query. This also means the expansion does not depend on
the data in your database. So postgresql continaually expands the
query, leading to your infinite recursion error.
I just found out
This is just to report success: I dropped all indices and repeated:
UPDATE intwfs SET id = nextval('myseq');
and it worked fine - took 3681 secs (my estimate of an hour wasn't far
out). Now doing a VACUUM FULL to remove the old tuples.
--
Clive Page
Dept of Physics & Astronomy,
University o
Howdy Michael,
Thanks for the help. I 'm presently using 8.0-beta2 on Windows. I
will upgrade that to 8.0 release today. However, my production server
is 7.4.2 (on Linux), and I'm somewhat reticent to migrate to 8.0 because
it is still pretty new. I belive I came across a message that ind
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Sat, 8 Jan 2005, Esteban Kemp wrote:
I'm starting to develop a production enviroment with Postgres and Tomcat, And I
have to choose between some free linux distribution like:
whitebox
RHEL
RHEL is not free (of charge).
Fedora
Suse
SLES is again
On Wed, 19 Jan 2005 03:32:05 -0800, J. Greenlees <[EMAIL PROTECTED]> wrote:
> Dick Davies wrote:
> > http://www.postgresql.org
> >
> > looks bloody awful in firefox on debian, until I switch font
> > (on the site) from 'normal' to 'large'.
> >
> > Anyone else seeing that? I'm sure it was fine a cou
I'm starting to develop a production enviroment
with Postgres and Tomcat, And I have to choose between some free linux
distribution like:
whiteboxRHELFedora
Suse
Which is the better distribution in terms of
postgres? if this has an answer
I have a rule similar to this:
CREATE RULE rule_branch_delete AS
ON DELETE TO tree
DO DELETE
FROM tree
WHERE ancestor_id IS NOT NULL
AND OLD.child_id = ancestor_id;
The data is oraganized like this:
ancestor_id child_id
NULL1
1
On Wed, 19 Jan 2005, Richard Huxton wrote:
> Hmm - wonder if there might be some memory leak in updates to the R-tree
> - it gets used less than B-tree, so it could be. If you reply to this,
> make sure you mention your version of PG - one of the developers might
> know more. Probably also worth l
pgEdit 1.0 (http://pgedit.com/) is a high performance SQL editor and
development environment for PostgreSQL. pgEdit features include SQL
syntax coloring, direct source code execution, Unicode support,
integrated documentation, and extensive customizable editing
facilities. pgEdit is available f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
- -
PostgreSQL New RPM Set
2005-01-19
Version: 8.0.0
Set labels: 8.0.0-1PGDG
- -
- --
After more than a year of hard work, the PostgreSQL Global Development
Group proudly announces the release of version 8.0.0 of the PostgreSQL
ORDBMS. This release involves possibly more major changes than any prior
version of PostgreSQL since 6.3, including:
Native Windows port
Savepoints/nest
Jamie Deppeler wrote:
Trigger
CREATE TRIGGER "new_trigger" AFTER INSERT OR UPDATE
ON "chargeratetest" FOR EACH ROW
EXECUTE PROCEDURE "chargeratetest"();
function
CREATE OR REPLACE FUNCTION "chargeratetest" () RETURNS trigger AS'
begin
UPDATE chargeratetest
set notes=''hello''
where new."primary"
Clive Page wrote:
On Wed, 19 Jan 2005, Richard Huxton wrote:
Nothing wrong with what you're doing, however, you are running a
transaction that touches 142 million rows (expiring the old rows and
adding new ones). Still, unless you are particularly short of memory, or
haven't tuned PostgreSQL it sh
On Wed, Jan 19, 2005 at 12:20:23PM +0100, Marco Colombo wrote:
> On Tue, 18 Jan 2005, Tom Lane wrote:
> >>followed by linefeed). On Macintosh, it is the ASCII CR (return)
> >>character."
> >
> >Seems like Guido has missed a bet here: namely the case of a script
> >generated on one platform and fed
On Tue, 18 Jan 2005 10:38:24 -0800, Chris wrote:
> The DBD::Pg man page say's this about cursors. What I don't
> understand is the nested selects being in a different transactions.
> Can someone clarify for me what is being said here? Does this
> basically mean that I can use cursors in DBD::Pg, I
Dick Davies wrote:
http://www.postgresql.org
looks bloody awful in firefox on debian, until I switch font
(on the site) from 'normal' to 'large'.
Anyone else seeing that? I'm sure it was fine a couple of weeks back.
don't know about the fonts, but 15 minutes and still trying to load it.
several oth
On Tue, 18 Jan 2005, Tom Lane wrote:
Michael Fuhr <[EMAIL PROTECTED]> writes:
http://docs.python.org/ref/physical.html
"A physical line ends in whatever the current platform's convention
is for terminating lines. On Unix, this is the ASCII LF (linefeed)
character. On Windows, it is the ASCII seq
On Wed, Jan 19, 2005 at 09:35:15AM +, Clive Page wrote:
> I have a largish table (71 million rows) to which I needed to add a new
> integer column containing a unique identifier - a simple sequence seemed
> to be good enough. I discovered the CREATE SEQUENCE command which looked
> as if it wou
On Wed, 19 Jan 2005, Richard Huxton wrote:
> Nothing wrong with what you're doing, however, you are running a
> transaction that touches 142 million rows (expiring the old rows and
> adding new ones). Still, unless you are particularly short of memory, or
> haven't tuned PostgreSQL it should be fi
1 - 100 of 109 matches
Mail list logo
