On Wed, 6 Jun 2001, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > Yes, column = NULL should *never* return true according to the spec (it
> > should always return NULL in fact as stated). The reason for breaking
> > with the spec is AFAIK to work with broken microsoft clients
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> As far as I know, this is the standard (ASCII-ordered) way of sorting text.
No, it's the "we don't know anything about text, but we can compare
their numeric values" approach.
--
Trond Eivind Glomsrød
Red Hat, Inc.
Stephan Szabo <[EMAIL PROTECTED]> writes:
> Yes, column = NULL should *never* return true according to the spec (it
> should always return NULL in fact as stated). The reason for breaking
> with the spec is AFAIK to work with broken microsoft clients that seem to
> think that =NULL is a meaningfu
> Tatsuo Ishii writes:
>
> > I don't understand following behavior of psql:-)
> > This is PostgreSQL 7.1.2 on Linux.
>
> I think you're still running the 7.1.1 version of psql, because this is
> one bug fixed in 7.1.2. Try 'psql --version'.
You are right. I seem to mixed up 7.1.1 psql with 7.1
[EMAIL PROTECTED] ,in message <200106062214.f56ME2E51506@postg
resql.org>, wrote:
> First it's not standard SQL, so chances aren't that good.
> Second, how do you think the system should behave in the
> following case:
>
> * Table A has one trigger BEFORE IN
Eric writes:
>I can realize this function in the SYBase,but How can i do it in the PostgreSQL?
>
> /SQL***/
> if not exists(select id from test) insert into test(id) values (280);
> /*/
I don't know if this is SQL92, but
insert into test(id) select 280 where not exists(select i
"Joe Conway" <[EMAIL PROTECTED]> writes:
> I wasn't quite sure if there are changes I can/should make to
> has_table_privilege based on this discussion.
My feeling is that the name-based variants of has_table_privilege should
perform downcasing and truncation of the supplied strings before trying
[EMAIL PROTECTED] (Nathan Myers) writes:
> On Tue, Jun 05, 2001 at 08:01:02PM -0400, Tom Lane wrote:
>> Thoughts? Is there anything about this that might be unsafe? Should
>> QueryCancel be set after *any* failure of recv() or send(), or only
>> if certain errno codes are detected (and if so, wh
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> There is a "postgres" option -o which can redirect the server output to a
> file. The postmaster output will still go to stderr. Does anyone recall
> how this was supposed to be useful?
That code is, um, ancient. I recall having seen comments to t
On Tue, Jun 05, 2001 at 08:01:02PM -0400, Tom Lane wrote:
>
> Thoughts? Is there anything about this that might be unsafe? Should
> QueryCancel be set after *any* failure of recv() or send(), or only
> if certain errno codes are detected (and if so, which ones)?
Stevens identifies some errno c
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> So, this is one of those "known problem, improved in v7.2" sort of issues?
Yup.
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the un
Great, thanks :)
On Wed, 6 Jun 2001, Tom Lane wrote:
> The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > So, this is one of those "known problem, improved in v7.2" sort of issues?
>
> Yup.
>
> regards, tom lane
>
Marc G. Fournier ICQ#7615664
Okay, based on 5k records and a "couple of wallclock minutes" being equal
to ~120sec, you are getting 41 inserts/sec?
On Wed, 6 Jun 2001, KuroiNeko wrote:
> > Build a file with 100k INSERT statements in it, and run psql -f on that
> > file ... no BEGIN/END in the file, just straight INSERTs
On Wed, 6 Jun 2001, Tom Lane wrote:
> The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > The 4m:30s is running one process for 100K inserts ... with two
> > CPUs/processes, it increases the time to process by almost 40% ... ?
>
> Do you mean two processes inserting into the same table?
Yup ..
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Does anyone want to keep elog(NOIND)? It's not used anywhere, and I think
> the notion of indentation levels, while kind of obsolete with syslog
> anyway, should not be part of the elog API.
Nuke it.
While you're at it, rearrange the numeric order
Hi,
I am trying to use postgresql in a research
project. I need to add several new operators, some
will probably take more than 2 input tuple streams.
The new operator will be considered by optimizer
when estimating cost and choosing a plan.
Can anyone tell me how hard this will be? And
where
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> The 4m:30s is running one process for 100K inserts ... with two
> CPUs/processes, it increases the time to process by almost 40% ... ?
Do you mean two processes inserting into the same table?
I committed some changes recently that reduce the
Morning all ...
Have a client that is running an HP server, specs as follows:
> HP-UX 11.00 HP 9000 L-200, Dual CPU (400MHz - 64 bit),
> OS Disk: 9GB U2W-LVD SCSI, 10K rpm
They are trying to determine whether or not it will be able to
handle their environment, and we're trying
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> One way to do this that wouldn't involve breaking the protocol is
>> to assign significance to linebreaks in an 'E' message's payload.
> Some fields may contain line breaks; for example, error messages
> definitely do now.
Yes.
> Build a file with 100k INSERT statements in it, and run psql -f on that
> file ... no BEGIN/END in the file, just straight INSERTs ... what is the
> max throughput ppl can see?
H Depends. Inserting up to 5,000 of Apache log records takes no
longer than a couple of wallclock minut
>> if not exists(select id from test) insert into test(id) values (280);
> Write a function in PL/pgSQL.
That particular case could be handled like so:
insert into test(id) select 280 where not exists(select id from test);
The select produces either zero or one row depending on whether its
WHE
With XSDs right around the corner using ISO 8601 compliant dates, what
are the chances Postgres could fully support them?
The primary difference between that and what it does now is a T for
the date / time seperator rather than a space and the potential for a
Z for the timezone seperator.
I'm co
Hi all,
I am trying to delete a record which had one of the fields as oid.
I was able to delete all the records except for 3.
I tried:
select lo_unlink(64445) from tablename
And then:
delete from tablename where id=1;
it worked
But for 3 records the delete command goes in hang.
on executing:
Hi all,
I am having problems deleting a record with oid. I tried
select lo_unlink(68778) from tablename
where 68778 is the oid
but it gives :
lo_unlink
---
-1
-1
(2 rows)
and when I try to delete that record by:
delete from tablename where id=1;
it goes on hang.
I want
Alessio Bragadini <[EMAIL PROTECTED]> writes:
> FATAL 2: ZeroFill(/data/postgres/pg_xlog/xlogtemp.1223) failed: No such
> file or directory
I think you ran out of disk space. The error message is misleading :-(
regards, tom lane
---(end of broad
Peter Eisentraut <[EMAIL PROTECTED]> writes:
>> It'd be better to allow ErrorResponse to carry multiple fields.
> That's the idea. But I can hardly concatenate the error codes, can I? I
> looks as though we need an API where all the messages (errors + notices)
> from each query cycle are collec
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> I don't understand following behavior of psql:-)
I can't replicate that misbehavior. I'm not using MULTIBYTE though,
maybe it depends on that ...
regards, tom lane
---(end of broadcast)--
"Magnus Naeslund\(f\)" <[EMAIL PROTECTED]> writes:
> I have a cronjob that does a vacuumdb -a -z every night.
> When i came to work this morning i saw a lot of postgres processes hanging
> on wait.
Sounds to me like you have an open transaction that is holding a lock
that everybody else needs. V
Morning all ...
Build a file with 100k INSERT statements in it, and run psql -f on
that file ... no BEGIN/END in the file, just straight INSERTs ... what is
the max throughput ppl can see?
I'm seeing reports of it maxing out on an AIX around 450, and on
an HP around 380 ... anyo
I don't understand following behavior of psql:-)
This is PostgreSQL 7.1.2 on Linux.
--
Tatsuo Ishii
$ psql pgimage
Welcome to psql, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help on internal slash commands
I have a cronjob that does a vacuumdb -a -z every night.
When i came to work this morning i saw a lot of postgres processes hanging
on wait.
The last thing i see before it hangs is this:
-
NOTICE: --Relation pg_toast_1216--
NOTICE: Pa
>
> hi,
>
> i am developing an application using php and postgresql. i do not
> know how to capture the return values of functions (stored
> procedures) from php.
>
select myfunction(parameter) ;
---(end of broadcast)---
TIP 5: Have
> Hello...
>
> Why does Postgresql order the uppercase letters first?
>
> I have e.g. a table with one row an in this row there are follow
> values:
>
> row1
>
> ADC
> aa
> ABC
>
> With this select-syntax
>
> select * from table order by row1
>
> I become this output
>
> ABC
> ADC
> a
Hello...
Why does Postgresql order the uppercase letters first?
I have e.g. a table with one row an in this row there are follow values:
row1
ADC
aa
ABC
With this select-syntax
select * from table order by row1
I become this output
ABC
ADC
aa
but I want this ouptut:
aa
ABC
ADC
What
hi,
i am developing an application using php and postgresql. i do not know how to capture the return values of functions (stored procedures) from php.
please reply to [EMAIL PROTECTED]
thanking you profusely,
prasanna.vDo You Yahoo!?
Yahoo! Mail Personal Address -
Get email at your
Severin Olloz wrote:
> Why does Postgresql order the uppercase letters first?
Do you have any LOCALE configuration in place?
--
Alessio F. Bragadini[EMAIL PROTECTED]
APL Financial Services http://village.albourne.com
Nicosia, Cyprus phone: +357-2-755750
"I
> We have deliberately avoided trying to abort as soon as the connection
> drops, for fear that that might cause unexpected problems.
Isn't there the additional worry, that if the backend does not abort,
that the client might not even notice the error (receives the next packet
which happens to b
At 18.13 05/06/01 -0400, Tom Lane wrote:
>Roberto Fichera <[EMAIL PROTECTED]> writes:
> > My first think was to bypass the SQL translation and use the Postgresql
> low
> > level routines.
> > I need to see the tables as record oriented archive, so I can scan
> > sequentially (forward and
> > bac
38 matches
Mail list logo
