> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Michael
> Glaesemann
> Sent: Wednesday, October 19, 2005 11:24 PM
> On Oct 20, 2005, at 14:50 , Dean Gibson (DB Administrator) wrote:
>> PSQL has the option to output the result of queries in several
>>
On Wed, Oct 19, 2005 at 11:04:36PM -0700, CSN wrote:
> So, does NULL != 'abc' always evaluate to false?
It never evaluates to false -- it evaluates to NULL.
http://www.postgresql.org/docs/8.0/interactive/functions-comparison.html
The ordinary comparison operators yield null (signifying "unknow
On Oct 20, 2005, at 15:04 , CSN wrote:
So, does NULL != 'abc' always evaluate to false? The
manual
(http://www.postgresql.org/docs/8.0/interactive/functions-
comparison.html)
states don't compare NULL values using =, but nothing
about using !=
The SQL standard way of checking for NULL is us
Am Mittwoch, den 19.10.2005, 21:05 +0100 schrieb Ledina Hido:
> On 19 Oct 2005, at 16:05, codeWarrior wrote:
>
> > You can also reverse engineer a postgreSQL RDBMS using an ODBC
> > driver and
> > MicroSloth's Visio.
Were you sucessfully w/ it? If so, which exact versions of all?
(PG, Visio
On Oct 20, 2005, at 14:50 , Dean Gibson (DB Administrator) wrote:
PSQL has the option to output the result of queries in several
different formats, including HTML. Suggestion: have an option to
output query results in XML format. Suggested format:
My personal opinion on this is that the
Tom Lane <[EMAIL PROTECTED]> writes:
> Chris Travers <[EMAIL PROTECTED]> writes:
> > If I understand the spec correctly, it seems to indicate that this is
> > specific to the locale/character set.
>
> The spec associates padding behavior with collations, which per spec are
> separate from the da
Am Mittwoch, den 19.10.2005, 22:04 +0200 schrieb Tino Wildenhain:
> Am Mittwoch, den 19.10.2005, 16:29 -0300 schrieb Marc G. Fournier:
> > I'm CC'ng this over to -hackers ... Tom? Comments?
> >
> ...
> > >> Then we are broken too :)
> > >>
> > >> # select 'a ' = 'a ';
> > >> ?column?
> > >> -
I was trying this:
IF (OLD.value != NEW.value) THEN
--
END IF;
and couldn't get the condition to evaluate to true at
all if OLD.value was NULL. I also tried:
IF (OLD.value NOT LIKE NEW.value) THEN
--
END IF;
with the same result. But this works:
IF ((OLD.value is NULL and NEW.value is NOT NU
PSQL has the option to output the result of queries in several different
formats, including HTML. Suggestion: have an option to output query
results in XML format. Suggested format:
field-1 value
field-2 value
etc. The user would be responsible for adding the enclosing XML.
NULL value
hi all
i am facing a problem and here it is:
i install the following (postgres) rpms as
root
postgresql-libs-8.0.0-1PGDG.i686.rpm
postgresql-8.0.0-1PGDG.i686.rpm
and
postgresql-server-8.0.0-1PGDG.i686.rpm
now i try to create a database
/usr/bin/createdb temp
when i connect to it
it s
Hi
I am doing my first installation of PostgreSQL in a
unix environment. I am installing on FreeBSD.
I have installed PostgreSQL Server 8.0.4, all
available postgreSQL contrib modules and PGAdminIII, but it still seems like the
"Admin Module" that gets installed with PGAdmin is not present
Tom Lane <[EMAIL PROTECTED]> writes:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
>> Of course, Oracle could tank the market by offering support at
>> un-competitive prices, but I can't think of a reason for them to do that
>> off the top of my head.
>
> They might hope that they could drive the e
Title: Re: [GENERAL] server , client encoding issue
i checked the locale it is
giving:
LANG=en_US.iso885915LC_CTYPE="en_US.iso885915"LC_NUMERIC=en_USLC_TIME="en_US.iso885915"LC_COLLATE="en_US.iso885915"LC_MONETARY="en_US.iso885915"LC_MESSAGES="en_US.iso885915"LC_PAPER="en_US.iso885915"LC_
Title: Re: [GENERAL] server , client encoding issue
how can i check my
environment ? i mean the locale settings?
From: Richard Huxton
[mailto:[EMAIL PROTECTED]Sent: Tue 10/18/2005 6:04 PMTo:
surabhi.ahujaCc: pgsql-general@postgresql.orgSubject: Re:
[GENERAL] server , client encoding is
Chris Travers <[EMAIL PROTECTED]> writes:
> If I understand the spec correctly, it seems to indicate that this is
> specific to the locale/character set.
The spec associates padding behavior with collations, which per spec are
separate from the datatypes --- that is, you should be able to able to
"Dann Corbit" <[EMAIL PROTECTED]> writes:
> Would you want varchar(30) 'Dann Corbit' to compare equal to bpchar(30)
> 'Dann Corbit'?
> I would.
And your point is?
regression=# select varchar(30) 'Dann Corbit' = char(30) 'Dann Corbit';
?column?
--
t
(1 row)
On Wed, 2005-10-19 at 19:26 -0700, CSN wrote:
> I'm trying to set up a trigger that simply updates a
> field's corresponding timestamp to now() whenever the
> field is updated. But it's not working. Trying to
> debug, I commented out the inner IF and END and the
> log seemed to indicate infinite re
CSN <[EMAIL PROTECTED]> writes:
> I'm trying to set up a trigger that simply updates a
> field's corresponding timestamp to now() whenever the
> field is updated. But it's not working. Trying to
> debug, I commented out the inner IF and END and the
> log seemed to indicate infinite recursion occur
> I'm trying to set up a trigger that simply updates a
> field's corresponding timestamp to now() whenever the
> field is updated. But it's not working. Trying to
> debug, I commented out the inner IF and END and the
> log seemed to indicate infinite recursion occurred. My
> next guess is that perh
Lyubomir Rusanov wrote:
> Hi,
> I am also interested in helping building Bulgarian translation for
> PostgreSQL.
> I think that we will not have enough time for 8.1 but maybe for 8.2.
The best you could do is submit your incremental improvements for 8.1,
so there is at least _some_ translation.
Josh Berkus wrote:
Dann,
I think that whatever is done ought to be whatever the standard says.
If I misinterpret the standard and PostgreSQL is doing it right, then
that is fine. It is just that PostgreSQL is very counter-intuitive
compared to other database systems that I have used in thi
I'm trying to set up a trigger that simply updates a
field's corresponding timestamp to now() whenever the
field is updated. But it's not working. Trying to
debug, I commented out the inner IF and END and the
log seemed to indicate infinite recursion occurred. My
next guess is that perhaps NULL's i
On Wed, 19 Oct 2005 15:40:44 -0300 (ADT)
"Marc G. Fournier" <[EMAIL PROTECTED]> wrote:
> On Wed, 19 Oct 2005, [EMAIL PROTECTED] wrote:
>
> > I was referring to trailing blanks, but did not explicitly say it,
> > though showed it in the examples. I am pretty sure that the SQL
> > standard says
Terry Fielder wrote:
Converting ' ' to '', well, that depends on the definition of the
datatype PAD/NOPAD ad nasuem.
Converting '' to NULL, that's just wrong, and here's some examples of
why:
In oracle, there is no easy way to determine the difference between
"there is no value" and "the
Dann Corbit wrote:
Doesn't NO PAD connect to the collating sequence (CS) rather than the
data type?
ISO/IEC 9075-2:1999 (E) (c)ISO/IEC
4.2 Character strings
A character set is described by a character set descriptor. A character
set descriptor includes:
- The name of the character set.
- The na
Converting ' ' to '', well, that depends on the definition of the
datatype PAD/NOPAD ad nasuem.
Converting '' to NULL, that's just wrong, and here's some examples of why:
In oracle, there is no easy way to determine the difference between
"there is no value" and "the value the user entered w
If there is a significant performance benefit to not expanding text columns in
comparison operations, then it seems it should be OK.
I probably read the standard wrong, but it seems to me that varchar, char, and
bpchar columns should all behave the same (e.g. if you do not expand with
or the P
Dann,
> I think that whatever is done ought to be whatever the standard says.
> If I misinterpret the standard and PostgreSQL is doing it right, then
> that is fine. It is just that PostgreSQL is very counter-intuitive
> compared to other database systems that I have used in this one
> particular
On Tue, 2005-18-10 at 22:21 -0500, Tony Caduto wrote:
> From what i understand Postgresql will scale with more cpus, but not in
> the same way as threaded server would.
Threading isn't really relevant. PostgreSQL currently forks a new
process for each client connection, and each process can be s
On 10/19/2005 3:46 PM, Dann Corbit wrote:
Would you want varchar(30) 'Dann Corbit' to compare equal to bpchar(30)
'Dann Corbit'?
I would.
wieck=# select 'Jan'::varchar(20) = 'Jan'::char(20);
?column?
--
t
(1 row)
wieck=# select 'Jan'::char(20) = 'Jan'::varchar(20);
?column?
-
> -Original Message-
> From: Martijn van Oosterhout [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 19, 2005 2:46 PM
> To: Dann Corbit
> Cc: Terry Fielder; Tino Wildenhain; Marc G. Fournier;
> [EMAIL PROTECTED]; pgsql-hackers@postgresql.org; pgsql-
> [EMAIL PROTECTED]
> Subject: Re: 'a
On Wed, Oct 19, 2005 at 02:05:20PM -0700, Dann Corbit wrote:
> > When the compared datatypes are VARCHAR: YES
>
> What is the value of doing that?
>
> I can see plenty of harm and absolutely no return. We are talking about
> blank padding before comparison. Do you really want 'Danniel '
> consi
Okay, since the standard explicitly says that whether 'a' = 'a ' is a
well-defined characteristic of a character datatype (NO PAD) I'm happy with
both Oracle and PostgreSQL. If you want a certain behavior, choose your
datatypes wisely. Cool. I didn't in a recent port. Uncool. I went from
CHAR(
"Dann Corbit" <[EMAIL PROTECTED]> wrote on 10/19/2005 04:33:23 PM:
> Doesn't NO PAD connect to the collating sequence (CS) rather than the
> data type?
Yep. Back to the mental drawing board.
BTW, the ordering of posts when they come to my mailbox is really weird.
>
> ISO/IEC 9075-2:1999 (E)
On Wed, 19 Oct 2005, Dann Corbit wrote:
> > -Original Message-
> > From: Terry Fielder [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, October 19, 2005 2:05 PM
> > To: Dann Corbit
> > Cc: Tino Wildenhain; Marc G. Fournier; [EMAIL PROTECTED];
> > pgsql-hackers@postgresql.org; pgsql-general@p
> -Original Message-
> From: Stephan Szabo [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 19, 2005 2:34 PM
> To: Dann Corbit
> Cc: Terry Fielder; Tino Wildenhain; Marc G. Fournier;
> [EMAIL PROTECTED]; pgsql-hackers@postgresql.org; pgsql-
> [EMAIL PROTECTED]
> Subject: Re: [HACKERS] '
Doesn't NO PAD connect to the collating sequence (CS) rather than the
data type?
ISO/IEC 9075-2:1999 (E) (c)ISO/IEC
4.2 Character strings
A character set is described by a character set descriptor. A character
set descriptor includes:
- The name of the character set.
- The name of the default coll
This is the salient sentence from the standard (that I've never personnally
thought much about before now).
"If CS has the NO PAD characteristic, then the pad character is an
implementation-dependent character different from any character in the
character set of X and Y that collates less than any
Chris Browne wrote:
[EMAIL PROTECTED] ("Merlin Moncure") writes:
No, that doesn't seem to follow ... if Oracle are spending their
resources to attack MySQL rather than us, the conclusion would be
that they are clearly still more informed by "the buzz" than
technical merit.
With no
Doug Quale wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
>
>> On Wed, 19 Oct 2005, [EMAIL PROTECTED] wrote:
>>
>>> I was referring to trailing blanks, but did not explicitly say it,
>>> though showed it in the examples. I am pretty sure that the SQL
>>> standard says that trailing whit
> -Original Message-
> From: Terry Fielder [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 19, 2005 2:05 PM
> To: Dann Corbit
> Cc: Tino Wildenhain; Marc G. Fournier; [EMAIL PROTECTED];
> pgsql-hackers@postgresql.org; pgsql-general@postgresql.org
> Subject: Re: 'a' == 'a ' (Was: RE: [p
Dann Corbit wrote:
Try this query in Oracle, SQL*Server, DB/2, Informix, etc.:
connxdatasync=# select 1 where cast('a' as varchar(30)) = cast('a ' as
varchar(30));
?column?
--
(0 rows)
I see how you can interpret the SQL Standard to make the above response
a correct one. But is it t
Hi Dann
Without looking at the internals to see if the 1 column or the other is
being converted to the other columns type before the compare, it really
demonstrates nothing.
It could perhaps be used to help demonstrate that when comparing a
datatype of CHAR to VARCHAR that
MS-SQL converts t
1.The sintax for create table is :
CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } ] TABLE table_name (
{ column_name data_type [ DEFAULT default_expr ] [ column_constraint [
... ] ] ...
What mean the parameter GLOBAL|LOCAL ??
2. in pg_class it is a field "relisshared" how can i use it ?
create table fooa (col1 varchar(30))
go
create table bara (col1 varchar(300))
go
insert into fooa values ('Danniel ')
go
insert into bara values ('Danniel ')
go
select * from fooa,bara where fooa.col1=bara.col1
go
Returns:
Danniel Danniel
I think that the issue is:
Does PostgreSQL us
"Guy Rouillier" <[EMAIL PROTECTED]> writes:
> Tino Wildenhain wrote:
> >
> > experiment=# SELECT 'a '::char = 'a '::char;
> > ?column?
> > --
> > t
> >
>
> This does't show anything useful, because the ::char casting simply
> takes the first char of any string:
>
> select 'abc'::char
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-general-
> [EMAIL PROTECTED] On Behalf Of Doug Quale
> Sent: Wednesday, October 19, 2005 1:10 PM
> To: pgsql-general@postgresql.org
> Subject: Re: [pgsql-advocacy] [GENERAL] Oracle buys Innobase
>
> "Marc G. Fournier" <[EMAIL PRO
create table foo (col1 varchar(30))
go
create table bar (col1 char(30))
go
insert into foo values ('Danniel ')
go
insert into bar values ('Danniel ')
go
select * from foo,bar where foo.col1=bar.col1
go
Result set:
Danniel Danniel
> -Original Message-
> Fro
Try this query in Oracle, SQL*Server, DB/2, Informix, etc.:
connxdatasync=# select 1 where cast('a' as varchar(30)) = cast('a ' as
varchar(30));
?column?
--
(0 rows)
I see how you can interpret the SQL Standard to make the above response
a correct one. But is it the response that you wo
Tino Wildenhain wrote:
Then we are broken too :)
# select 'a ' = 'a ';
?column?
--
f
(1 row)
>
>
> experiment=# SELECT 'a '::char = 'a '::char;
> ?column?
> --
> t
>
This does't show anything useful, because the ::char casting s
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> On Wed, 19 Oct 2005, [EMAIL PROTECTED] wrote:
>
>> I was referring to trailing blanks, but did not explicitly say it,
>> though showed it in the examples. I am pretty sure that the SQL
>> standard says that trailing whitespace is insignificant in s
I agree with you, but...
Actually that's not how the compare works usually.
Generally one of the operands is converted to the same datatype as the
other, and THEN the compare is performed.
I expect MS SQL is converting a 'sdas' typeless string to be assumed
CHAR and Postgresql is converting
Am Mittwoch, den 19.10.2005, 16:29 -0300 schrieb Marc G. Fournier:
> I'm CC'ng this over to -hackers ... Tom? Comments?
>
> On Wed, 19 Oct 2005, Dann Corbit wrote:
>
> > Yes, clearly that is the wrong result according to the SQL standard.
> >
> > Here is a SQL*Server query:
> > select 1 where 'a
On 19 Oct 2005, at 16:05, codeWarrior wrote:
You can also reverse engineer a postgreSQL RDBMS using an ODBC
driver and
MicroSloth's Visio.
"Bruno Cochofel" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Hi you all,
His there any SW that can do reverse engineering on pos
Given this part of that same rule applied to the strings:
"b) If the length in characters of X is not equal to the length in
characters of Y, then the shorter string is effectively replaced, for
the purposes of comparison, with a copy of itself that has been extended
to the length of the longer str
Would you want varchar(30) 'Dann Corbit' to compare equal to bpchar(30)
'Dann Corbit'?
I would.
If both are considered character types by the language, then they must
compare that way.
Perhaps there are some nuances that I am not aware of. But that is how
things ought to behave, if I were kin
On Wed, 19 Oct 2005, Dann Corbit wrote:
-Original Message-
From: Stephan Szabo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 19, 2005 12:39 PM
To: Dann Corbit
Cc: Marc G. Fournier; [EMAIL PROTECTED]; pgsql-
[EMAIL PROTECTED]
Subject: Re: [pgsql-advocacy] [GENERAL] Oracle buys Innoba
On Wed, 19 Oct 2005, Dann Corbit wrote:
> Yes, clearly that is the wrong result according to the SQL standard.
>
> Here is a SQL*Server query:
> select 1 where 'a' = 'a ' AND 'a' = 'a ' AND 'a ' = 'a '
>
> It returns (correctly): 1
Doesn't that depend on the collating sequence in use, or
> -Original Message-
> From: Stephan Szabo [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 19, 2005 12:39 PM
> To: Dann Corbit
> Cc: Marc G. Fournier; [EMAIL PROTECTED]; pgsql-
> [EMAIL PROTECTED]
> Subject: Re: [pgsql-advocacy] [GENERAL] Oracle buys Innobase
>
> On Wed, 19 Oct 2005,
I'm CC'ng this over to -hackers ... Tom? Comments?
On Wed, 19 Oct 2005, Dann Corbit wrote:
Yes, clearly that is the wrong result according to the SQL standard.
Here is a SQL*Server query:
select 1 where 'a' = 'a ' AND 'a' = 'a ' AND 'a ' = 'a '
It returns (correctly): 1
-Orig
OK, I am not an expert on the SQL standard, but I thought the definition
varied by data type e.g. varchar <> bpchar
Terry
Marc G. Fournier wrote:
On Wed, 19 Oct 2005, [EMAIL PROTECTED] wrote:
I was referring to trailing blanks, but did not explicitly say it,
though showed it in the examples.
Yes, clearly that is the wrong result according to the SQL standard.
Here is a SQL*Server query:
select 1 where 'a' = 'a ' AND 'a' = 'a ' AND 'a ' = 'a '
It returns (correctly): 1
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-general-
> [EMAIL PROTECTED] On Behalf
On Wed, Oct 19, 2005 at 09:12:16PM +0300, Andrus wrote:
> I want to select the email addresses which are not valid:
>
> do not contain exactly one @ character,
> contain ; > < " ' , characters or spaces etc.
The rules that define a valid email address are more complex than
most people realize, an
Andrus wrote:
> I have a database of e-mail addresses.
>
> I want to select the email addresses which are not valid:
>
> do not contain exactly one @ character,
> contain ; > < " ' , characters or spaces etc.
>
> What is the WHERE clause for this ?
Please see a long, detailed thread in the arch
This might be handy:
http://www.databasejournal.com/img/email_val.sql
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-general-
> [EMAIL PROTECTED] On Behalf Of Andrus
> Sent: Wednesday, October 19, 2005 11:12 AM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] Select al
On Wed, 19 Oct 2005, [EMAIL PROTECTED] wrote:
I was referring to trailing blanks, but did not explicitly say it,
though showed it in the examples. I am pretty sure that the SQL
standard says that trailing whitespace is insignificant in string
comparison.
Then we are broken too :)
# select
On Wed, Oct 19, 2005 at 09:55:18AM -0700, William Yu wrote:
> Mark Rae wrote:
> >With the newer kernels you should find that a dual core will
> >be giving you about 80% increase over a single core.
>
> I'm not experiencing this problem right now because I have NUMA disabled
> in the BIOS. :)
T
Csaba Nagy <[EMAIL PROTECTED]> writes:
> I wonder how fair is the lock allocation of SELECT FOR UPDATE ?
> Is it fair, i.e. the first transaction which requested the lock will get
> it, or it is possible that new requests are served quicker ?
8.1 will guarantee first-come-first-served for row-leve
I have a database of e-mail addresses.
I want to select the email addresses which are not valid:
do not contain exactly one @ character,
contain ; > < " ' , characters or spaces etc.
What is the WHERE clause for this ?
Andrus.
---(end of broadcast)---
This is maybe a really newbie question, but, when I have an
SQL function like that:
$$
Insert into mytable (id, name) values ($1, $2);
$$
What return value suppose to return?
I need to know if there is a tool that convert oracle procedures and
triggers to plpgsql syntax. Please, can anybody tell me where do i download
it from?, i'll thank you a lot.
Rafael
_
Un amor, una aventura, compañía para un via
That's me and my project listed there. Glad to give PG the good press
it deserves, it's the least I could do. It's been a great db for us,
and we're looking forward to 8.1.
And thanks for the help that I received on the mailing list a few months
back that directly impacted this project. It
Csaba Nagy <[EMAIL PROTECTED]> writes:
> Now the remote connections are coming from Java (the JDBC driver),
Oh, there's your problem. 8.0 doesn't have very good support for
logging the extended-query protocol, which is what recent versions
of the JDBC driver like to use. 8.1 will be better I bel
From the ANSI/ISO SQL Standard:
"3) The comparison of two character strings is determined as follows:
a) Let CS be the collating sequence indicated in Subclause 4.2.3,
''Rules determining collating sequence usage'', based on the declared
types of the two character strings.
b) If the length in char
[EMAIL PROTECTED] wrote:
> Yep. It is not just limited to empty strings; An all blank string,
> no matter the number of characters, is stored as NULL. And a
I'm no big Oracle fan; I'm trying to convince my company to convert a
major database to PG. But I can't reproduce what you are saying here
"Marc G. Fournier" <[EMAIL PROTECTED]> wrote on 10/19/2005 01:02:15
PM:
> On Wed, 19 Oct 2005, [EMAIL PROTECTED] wrote:
>
> >
> >
> > [EMAIL PROTECTED] wrote on 10/19/2005 12:35:25 AM:
> >
> >> Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> >>> Strangely a pgsql to oracle exporter is a go
Mark Rae wrote:
On Wed, Oct 19, 2005 at 12:32:36AM -0700, William Yu wrote:
Expect to need to upgrade to later Linux cores though. Previous kernel
on this server was 2.6.9+ (FC3 64-bit) -- promptly kernel panic'd upon
install of the DCs. FC3 installer did the same thing. Went to FC4
(2.6.11+)
A "PostgreSQL to Oracle converter" might be a really big project.
Having ported an application from PostgreSQL (7.3) to Oracle 9i, as I
recall, my biggest problems were:
- Quoting issues: the original PostgreSQL application quoted
integer/numeric type, and Oracle will not allow that, so I had t
Hi all,
I wonder how fair is the lock allocation of SELECT FOR UPDATE ?
Is it fair, i.e. the first transaction which requested the lock will get
it, or it is possible that new requests are served quicker ?
TIA,
Csaba.
---(end of broadcast)---
TIP
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-general-
> [EMAIL PROTECTED] On Behalf Of Marc G. Fournier
> Sent: Wednesday, October 19, 2005 9:02 AM
> To: [EMAIL PROTECTED]
> Cc: pgsql-general@postgresql.org
> Subject: Re: [pgsql-advocacy] [GENERAL] Oracle buys Innobase
>
>
On Wed, 19 Oct 2005, [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote on 10/19/2005 12:35:25 AM:
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
Strangely a pgsql to oracle exporter is a good thing. It'd be a great
feature of PostgreSQL. Imagine how many people would start on
PostgreS
Well, I'm completely sure that long running queries from local
connections are logged, as I can see them in the log file. Quick queries
are not logged even for local connections, I tested that too...
And I'm also sure that I do have long running queries on remote
connections, our application logged
Alle 15:07, mercoledì 19 ottobre 2005, Richard Huxton ha scritto:
> Vittorio wrote:
> > In my Pentium 4 box 2GHz with 256 MB of RAM I run a pg server 8.0.3
> > under netbsd 2.0.2 in which among other tables there's a "huge" table
> > letture02 made of 657,000 records and 98 numerical columns.
> >
[EMAIL PROTECTED] ("Merlin Moncure") writes:
>> > No, that doesn't seem to follow ... if Oracle are spending their
>> > resources to attack MySQL rather than us, the conclusion would be
>> > that they are clearly still more informed by "the buzz" than
>> > technical merit.
>>
>> With no disrespect
Csaba Nagy <[EMAIL PROTECTED]> writes:
> I wonder if I understood correctly what log_min_duration_statement
> does... I set it to 2000, and the result is that all queries running
> more than 2 seconds on _local_ connections are logged, but long running
> queries on remote connections are not logged
Hi all,
Postgres version: 8.0.3
I wonder if I understood correctly what log_min_duration_statement
does... I set it to 2000, and the result is that all queries running
more than 2 seconds on _local_ connections are logged, but long running
queries on remote connections are not logged. Is this som
[EMAIL PROTECTED] wrote on 10/19/2005 12:35:25 AM:
> Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> > Strangely a pgsql to oracle exporter is a good thing. It'd be a great
> > feature of PostgreSQL. Imagine how many people would start on
> > PostgreSQL if they KNEW that one day they cou
You can also reverse engineer a postgreSQL RDBMS using an ODBC driver and
MicroSloth's Visio.
"Bruno Cochofel" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi you all,
>
> His there any SW that can do reverse engineering on postgreSQL
> databases? I need something that can
Tim Nelson <[EMAIL PROTECTED]> writes:
> I am getting division by zero on a calculated field ( sum(sales) is 0 )
> and I can't find a way around this. I figured out you can't use an
> aggregate in a where, and using having the parser must (obviously)
> evaluate the select fields before consider
Richard Huxton wrote:
Tim Nelson wrote:
I am getting division by zero on a calculated field ( sum(sales) is 0 )
It's a two-stage process, so you'll want a sub-query. Something like: ...
Thanks. That's a cool addition to my bag of tricks.
---(end of broadcast)-
On Wed, 2005-10-19 at 15:55 +0200, [EMAIL PROTECTED] wrote:
> Hi Sven
>
> Thanks for the help. This looks like the kind of info I needed.
> One question:
> You suggest that I use : pkg_add -r postgresql80-server. If this requires
> postgresql80-client, will it automatically download it and install
Hi,
I am also interested in helping building Bulgarian translation for
PostgreSQL.
I think that we will not have enough time for 8.1 but maybe for 8.2.
Regards
Lyubomir Rusanov
Ivan Pavlov wrote:
Peter Eisentraut wrote:
As the release of PostgreSQL 8.1 draws near, it is once aga
I think this probably belongs back on -advocacy, so I'm cc:ing there
so we can move it.
On Tue, Oct 18, 2005 at 03:16:23PM -0700, Chris Travers wrote:
> Interesting. So they are willing to appear ill-informed in public but
> better informed in private? To what end? That seems strange to me
Hi Sven
Thanks for the help. This looks like the kind of info I needed.
One question:
You suggest that I use : pkg_add -r postgresql80-server. If this requires
postgresql80-client, will it automatically download it and install? The
docs I have read suggest this, but maybe you can confirm?
Thanks
Hi Sven
Thanks for the info. This is a great help.
One question:
> On Wed, 2005-10-19 at 08:23 +0200, [EMAIL PROTECTED] wrote:
>> Hi
>>
>> I am very new to FreeBSD (Windows Background), but am busy trying to
>> implement a PostgreSQL database that I have running in the Windows
>> environemtn on F
On Wed, 2005-10-19 at 08:23 +0200, [EMAIL PROTECTED] wrote:
> Hi
>
> I am very new to FreeBSD (Windows Background), but am busy trying to
> implement a PostgreSQL database that I have running in the Windows
> environemtn on FreeBSD. Naturally, most of my problems so far have been
> geeting to grip
Tim Nelson <[EMAIL PROTECTED]> schrieb:
> I am getting division by zero on a calculated field ( sum(sales) is 0 ) and
> I can't find a way around this. I figured out you can't use an aggregate
> in a where, and using having the parser must (obviously) evaluate the
> select fields before consid
Tim Nelson <[EMAIL PROTECTED]> writes:
> I am getting division by zero on a calculated field ( sum(sales) is
> 0 ) and I can't find a way around this. I figured out you can't use
> an aggregate in a where, and using having the parser must
> (obviously) evaluate the select fields before considerin
On Oct 19, 2005, at 21:26 , Tim Nelson wrote:
I am getting division by zero on a calculated field ( sum(sales) is
0 ) and I can't find a way around this. I figured out you can't
use an aggregate in a where, and using having the parser must
(obviously) evaluate the select fields before con
Vittorio wrote:
In my Pentium 4 box 2GHz with 256 MB of RAM I run a pg server 8.0.3
under netbsd 2.0.2 in which among other tables there's a "huge" table
letture02 made of 657,000 records and 98 numerical columns.
Using psql
and the "heavy" view letture24btnondom (see below) I face the follo
1 - 100 of 128 matches
Mail list logo
