Peter Eisentraut <[EMAIL PROTECTED]> writes:
>> What's standard about it?
> ISO/IEC 9075-2:1999 clause 19.1 general rule 1 c) to be exact. ;-)
Hmm. Looks like we need a wholesale revision of command tags, indeed.
At least if we want to consider command tags to be the data that
satisfies this sp
"Rod Taylor" <[EMAIL PROTECTED]> writes:
> 7.2 crashes with the below function:
> CREATE OR REPLACE FUNCTION runMaintenance()
> RETURNS BOOL AS '
> VACUUM;
> SELECT TRUE;
> ' LANGUAGE sql;
Ugh. The problem is that VACUUM's implicit CommitTransaction calls
wipe out all the transient memory a
Gordon Runkle <[EMAIL PROTECTED]> writes:
> I'm dead in the water with pg_clog errors:
> Mar 19 18:25:05 nexus postgres[28736]: [6] FATAL 2: open of
> /data00/pgdata/pg_clog/007D failed: No such file or directory
Am I right in guessing that the range of file names you have present
in pgdata/clo
On Tue, 2002-03-19 at 21:40, Christopher Kings-Lynne wrote:
> 1. Implementing a byte-compatible query cache WILL improve the speed of
> repetitive queries over static data.
For some specific workloads, I think it has the potential to
significantly improve performance.
> 3. It is really hard to i
Hi folks,
I'm dead in the water with pg_clog errors:
Mar 19 18:25:05 nexus postgres[28736]: [6] FATAL 2: open of
/data00/pgdata/pg_clog/007D failed: No such file or directory
Mar 19 18:25:06 nexus postgres[22250]: [1] DEBUG: server process (pid
28736) exited with exit code 2
Mar 19 22:06:53 n
Hi folks,
I'm dead in the water with pg_clog errors:
Mar 19 18:25:05 nexus postgres[28736]: [6] FATAL 2: open of
/data00/pgdata/pg_clog/007D failed: No such file or directory
Mar 19 18:25:06 nexus postgres[22250]: [1] DEBUG: server process (pid 28736) exited
with exit code 2
Mar 19 22:06:53
> > Well, the simple query cache scheme that is currently being proposed
> > would use a byte-by-byte comparison of the incoming query. I think the
> > consensus is that for a lot of workloads, this would be a bad idea.
>
> And this is what I have been trying to argue. Many SQL
> deployments execu
Neil Conway wrote:
>
> On Tue, 2002-03-19 at 19:20, F Harvell wrote:
> > I feel that the caching should be SQL transparent. If it is
> > implemented reasonably well, the performance gain should be pretty
> > much universal.
>
> Well, the simple query cache scheme that is currently being propose
On Tue, 2002-03-19 at 19:20, F Harvell wrote:
> I feel that the caching should be SQL transparent. If it is
> implemented reasonably well, the performance gain should be pretty
> much universal.
Well, the simple query cache scheme that is currently being proposed
would use a byte-by-byte compari
On Tue, 19 Mar 2002 12:12:52 CST, "Ross J. Reedstrom" wrote:
> On Mon, Mar 18, 2002 at 09:35:51PM -0500, Neil Conway wrote:
> > >
> > > "It is an application issue"
> > > This is completely wrong. Caching can not be done against a database without
> > > knowledge of the database, i.e. when the da
Neil Conway <[EMAIL PROTECTED]> writes:
> In language bindings which wrap around the libpq C interface, should the
> fe_getauthname() function be used?
Seems like an internal routine to me.
regards, tom lane
---(end of broadcast)--
On Tue, 2002-03-19 at 15:30, Matthew Kirkwood wrote:
> On Tue, 19 Mar 2002, Oleg Bartunov wrote:
>
> Sorry to reply over you, Oleg.
>
> > On 13 Mar 2002, Greg Copeland wrote:
> >
> > > One of the reasons why I originally stated following the hackers list is
> > > because I wanted to implement bi
> I am thinking that a non-broken approach would involve (1) treating
> a domain as binary-compatible with its base type, and therefore with
> all other domains on the same base type, and (2) allowing a coercion
> function that produces the base type to be used to produce the
domain
> type. (The
On Tue, 19 Mar 2002, Oleg Bartunov wrote:
Sorry to reply over you, Oleg.
> On 13 Mar 2002, Greg Copeland wrote:
>
> > One of the reasons why I originally stated following the hackers list is
> > because I wanted to implement bitmap indexes. I found in the archives,
> > the follow link, http://w
The DOMAIN patch is completely broken when it comes to type coercion
behavior. For one thing, it doesn't know that any operators or
functions on a domain's base type can be used with a domain:
domain=# create domain zip as char(2);
CREATE
domain=# create table foo (f1 zip);
CREATE
domain=# selec
In language bindings which wrap around the libpq C interface, should the
fe_getauthname() function be used?
It's not declared in libpq-fe.h, which AFAIK is the only header file
that libpq applications should be using.
Cheers,
Neil
--
Neil Conway <[EMAIL PROTECTED]>
PGP Key ID: DB3C29FC
Tom Lane wrote:
> Christopher Quinn <[EMAIL PROTECTED]> writes:
>
>
> The WAL log uses per-record CRCs plus sequence numbers (both per-record
> and per-page) as a way of determining where valid information stops.
> I don't see any need for relying on a "root block" in the sense you
> describe.
>
Jan Wieck wrote:
>
> mlw wrote:
> > [...]
> >
> > IMHO modifying the function manager to allow the return of a full row, and a
> > "set of" full rows, answers a LOT of issues I have seen over the years with
> > PostgreSQL extensibility.
>
> Sure. Actually I think you'll have an easy project
On Tue, 19 Mar 2002, Marc G. Fournier wrote:
>
> do you know if any of the other lists are missing? or is it just -hackers
> that got lost?
Personaly me, I have missed all lists. fts.postgresql.org seems doesn't
recieving -hackers lists.
>
> On Tue, 19 Mar 2002, Oleg Bartunov wrote:
>
> > Than
On Tue, 19 Mar 2002, Bruce Momjian wrote:
> Oleg Bartunov wrote:
> > On Tue, 19 Mar 2002, Bruce Momjian wrote:
> >
> > > Oleg Bartunov wrote:
> > > > Bruce,
> > > >
> > > > we have something to add. It's quite important for users of our tsearch module.
> > > > Too late ?
> > >
> > > For 7.2.1, I
On Tue, 2002-03-19 at 15:52, mlw wrote:
> Dale Anderson wrote:
> >
> > Hello Group,
> >I need your help, in putting together a list of comparisons, and good solid
>technical reasons, to why to use PostgreSQL over using Microsoft SQL Server. Right
>now, we are using PostgreSQL for a back-en
I didn't have any messages from lists for ~ 2 months !
What's the problem ?
Regards,
Oleg
_
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Inter
Bruce,
we have something to add. It's quite important for users of our tsearch module.
Too late ?
On Mon, 18 Mar 2002, Bruce Momjian wrote:
>
> OK, I have branded 7.2.1 and updated HISTORY/release.sgml. Do we want
> any special text about the sequence bug fix, or just mention in the
> announce
Must have gotten unsubscribed from the list at some point ... just
re-added it now ...
On Tue, 19 Mar 2002, Oleg Bartunov wrote:
> Marc,
>
> I see no postings to hackers come to fts.postgresql.org for more than a
> month. Seems there is a problem, because I also didn't get *any* messages
> from
Thanks.
I'm getting messages now.
Oleg
On Tue, 19 Mar 2002, Marc G. Fournier wrote:
>
> Must have gotten unsubscribed from the list at some point ... just
> re-added it now ...
>
> On Tue, 19 Mar 2002, Oleg Bartunov wrote:
>
> > Marc,
> >
> > I see no postings to hackers come to fts.post
Marc,
I see no postings to hackers come to fts.postgresql.org for more than a
month. Seems there is a problem, because I also didn't get *any* messages
from psql mailing lists. I was subscribed to lists since 1995 and
want to stay in there. Could you please check the problem.
I was patient beca
Christopher,
I'm sorry it's too late, but I haven't receive any messages from
postgres mailing lists for a month (don't know why). Just found your
message in archives.
GiST is a great thing, it's generalised search tree invented by
Hellerstein in 1995. It allows you to define custom data type,
i
Greg,
if you're still in bitmap indices you may take a look on our
contrib/intarray module.
Regards,
Oleg
On 13 Mar 2002, Greg Copeland wrote:
> One of the reasons why I originally stated following the hackers list is
> because I wanted to implement bitmap indexes. I
Theoriginal problem was the low cpu usage due to semaphores, most of orange
zone is due to sems
thanks and regards
<>
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
On Mon, Mar 18, 2002 at 09:35:51PM -0500, Neil Conway wrote:
> >
> > "It is an application issue"
> > This is completely wrong. Caching can not be done against a database without
> > knowledge of the database, i.e. when the data changes.
>
> But can't this be achieved by using a LISTEN/NOTIFY mo
Tom Lane writes:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Peter Eisentraut wrote:
> >> There is a standard for this. CREATE DOMAIN shows CREATE DOMAIN.
>
> > OK, CVS changed to emit CREATE DOMAIN.
>
> What's standard about it?
ISO/IEC 9075-2:1999 clause 19.1 general rule 1 c) to be exact
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Peter Eisentraut wrote:
> >> There is a standard for this. CREATE DOMAIN shows CREATE DOMAIN.
>
> > OK, CVS changed to emit CREATE DOMAIN.
>
> What's standard about it? I count 9 existing statements that use
> "CREATE", vs 4 that
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Peter Eisentraut wrote:
>> There is a standard for this. CREATE DOMAIN shows CREATE DOMAIN.
> OK, CVS changed to emit CREATE DOMAIN.
What's standard about it? I count 9 existing statements that use
"CREATE", vs 4 that use "CREATE xxx". (And of those
Thomas Lockhart wrote:
> ...
> > I have applied the following new patch. It moves DROP DATABASE as you
> > suggested, and fixes the CREATE TABLE tag to show just CREATE and not
> > CREATE DOMAIN. Actually, CREATE DOMAIN should output just DOMAIN too,
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > I have applied the following new patch. It moves DROP DATABASE as you
> > suggested, and fixes the CREATE TABLE tag to show just CREATE and not
> > CREATE DOMAIN. Actually, CREATE DOMAIN should output just DOMAIN too,
> > unless someone can
Bruce Momjian writes:
> I have applied the following new patch. It moves DROP DATABASE as you
> suggested, and fixes the CREATE TABLE tag to show just CREATE and not
> CREATE DOMAIN. Actually, CREATE DOMAIN should output just DOMAIN too,
> unless someone can tell my why that is not consistent.
...
> I have applied the following new patch. It moves DROP DATABASE as you
> suggested, and fixes the CREATE TABLE tag to show just CREATE and not
> CREATE DOMAIN. Actually, CREATE DOMAIN should output just DOMAIN too,
> unless someone can tell my why that is not consistent.
Consistant or not
Adrian 'Dagurashibanipal' von Bidder wrote:
>
> On Tue, 2002-03-19 at 15:52, mlw wrote:
> > Dale Anderson wrote:
> > >
> > > Hello Group,
> > >I need your help, in putting together a list of comparisons, and good solid
>technical reasons, to why to use PostgreSQL over using Microsoft SQL Ser
Christopher Quinn <[EMAIL PROTECTED]> writes:
> I've been wondering how pgsql goes about guaranteeing data
> integrity in the face of soft failures. In particular
> whether it uses an alternative to the double root block
> technique - which is writing, as a final indication of the
> validity o
Gavin Sherry wrote:
> I'm not sure that cached results is a direction postgres need move in. But
> if it does, I think this a better way to do it (given that I may have
> overlooked something) than modifying the function manager (argh!).
I actually had an anterior motive.
Your comment about cach
On Tue, 2002-03-19 at 15:52, mlw wrote:
> Dale Anderson wrote:
> >
> > Hello Group,
> >I need your help, in putting together a list of comparisons, and
good solid technical reasons, to why to use PostgreSQL over using
Microsoft SQL Server. Right now, we are using PostgreSQL for a back-end
fo
Neil Conway <[EMAIL PROTECTED]> writes:
> My impression (I could be wrong) is that LISTEN/NOTIFY doesn't get
> the press that it deserves. If this model isn't widely used because
> of some deficiencies in the LISTEN/NOTIFY implementation, IMHO our
> time would be better spent fixing those problems
On 19 Mar 2002, Greg Copeland wrote:
> On Tue, 2002-03-19 at 07:46, mlw wrote:
> [snip]
>
> > Right now, the function manager can only return one value, or one set of values
> > for a column. It should be possible, but require a lot of research, to enable
> > the function manager to return a set
Jeff Davis <[EMAIL PROTECTED]> writes:
> A library implies that the application is running long enough to actually
> hear the notofication. Web apps start up, read from the database, and before
> any cache is needed they're done and the next one starts up, reading again
> from the database. On
Dale Anderson wrote:
>
> Hello Group,
>I need your help, in putting together a list of comparisons, and good solid
>technical reasons, to why to use PostgreSQL over using Microsoft SQL Server. Right
>now, we are using PostgreSQL for a back-end for some of our web stuff. A couple of
>our
do you know if any of the other lists are missing? or is it just -hackers
that got lost?
On Tue, 19 Mar 2002, Oleg Bartunov wrote:
> Thanks.
> I'm getting messages now.
>
> Oleg
> On Tue, 19 Mar 2002, Marc G. Fournier wrote:
>
> >
> > Must have gotten unsubscribed from the list at some p
On Tue, 2002-03-19 at 07:46, mlw wrote:
> I was thinking about this. There seems to be a consensus that caching means no
> ACID compliance. And everyone seems to think it needs to be limited. We can
> implement a non-ACID cache as a contrib function with some work to the function
> manager.
Until
OK, patch applied to 7.2.1 only --- no need to have that mentioned in
7.3 README.tsearch. HISTORY/release.sgml updated in both branches:
contrib/tsearch dictionary improvements, see README.tsearch for
an additional installation step (Thomas T. Thai, Teodor Sigaev)
-
On Tue, 2002-03-19 at 07:46, mlw wrote:
[snip]
> Right now, the function manager can only return one value, or one set of values
> for a column. It should be possible, but require a lot of research, to enable
> the function manager to return a set of rows. If we could get that working, it
> could
On a side note, is it possible that we could add the "iscachable" which
for now, would give cache bias? That is, allow for a mechanism to
indicate that the pages that are required for this query will be
frequently needed. I've not looked at the buffer cache implementation.
Is it possible to som
> Yes...I was thinking that a generic library interface with a nice design
> pattern might meet this need rather well. Done properly, I think we can
> make it where all that, more or less, would be needed is application
> hooks which accept the result set to be cached and a mechanism to signal
>
Oleg Bartunov wrote:
> On Tue, 19 Mar 2002, Bruce Momjian wrote:
>
> > Oleg Bartunov wrote:
> > > Bruce,
> > >
> > > we have something to add. It's quite important for users of our tsearch module.
> > > Too late ?
> >
> > For 7.2.1, I don't think it is too late but I don't think we can wait
> > d
On Tue, 19 Mar 2002, Bruce Momjian wrote:
> Oleg Bartunov wrote:
> > Bruce,
> >
> > we have something to add. It's quite important for users of our tsearch module.
> > Too late ?
>
> For 7.2.1, I don't think it is too late but I don't think we can wait
> days.
I'll do a wrap on Friday, if Oleg w
Christopher Kings-Lynne wrote:
> In latest CVS:
>
> template1=# create table test (a int4 not null);
> CREATE DOMAIN
> template1=#
Fixed.
test=> create table texst(x int);
CREATE
test=> \q
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PR
Thanks. Fixed.
---
Fernando Nasser wrote:
> Well,
>
> Someone just dropped the DROP DATABASE statement rules right in the
> middle of the CREATE DATABASE production rules!!!
>
> Fernando
>
>
>
> Fernando Nasser wrote:
Rod Taylor wrote:
> I truely don't know what I did to create the nasty patch (source file
> certainly didn't look like what it resulted in) -- then again there
> have been alot of changes since the domain patch was created.
>
> This should fix gram.y
>
> If anyone knows a better way of creating
Rod Taylor wrote:
> I truely don't know what I did to create the nasty patch (source file
> certainly didn't look like what it resulted in) -- then again there
> have been alot of changes since the domain patch was created.
Yes, that patch has been around for a while and I am sure went through
se
I truely don't know what I did to create the nasty patch (source file
certainly didn't look like what it resulted in) -- then again there
have been alot of changes since the domain patch was created.
This should fix gram.y
If anyone knows a better way of creating patches other than diff -rc ,
pl
It looks like diff / patch got confused and applied the changes in the
wrong places.
--
Rod Taylor
This message represents the official view of the voices in my head
- Original Message -
From: "Christopher Kings-Lynne" <[EMAIL PROTECTED]>
To: "Hackers" <[EMAIL PROTECTED]>; <[EMAIL PROTE
Oleg Bartunov wrote:
> Bruce,
>
> we have something to add. It's quite important for users of our tsearch module.
> Too late ?
For 7.2.1, I don't think it is too late but I don't think we can wait
days.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED]
D'Arcy J.M. Cain wrote:
> On March 18, 2002 06:12 pm, Bruce Momjian wrote:
> > OK, I have branded 7.2.1 and updated HISTORY/release.sgml. Do we want
> > any special text about the sequence bug fix, or just mention in the
> > announcement that all 7.2 people should upgrade?
>
> Does this mean that
On March 18, 2002 06:12 pm, Bruce Momjian wrote:
> OK, I have branded 7.2.1 and updated HISTORY/release.sgml. Do we want
> any special text about the sequence bug fix, or just mention in the
> announcement that all 7.2 people should upgrade?
Does this mean that I can start putting fixes and upgra
Hello,
I've been wondering how pgsql goes about guaranteeing data
integrity in the face of soft failures. In particular
whether it uses an alternative to the double root block
technique - which is writing, as a final indication of the
validity of new log records, to alternate disk blocks at
Le Lundi 18 Mars 2002 22:53, Dale Anderson a écrit :
> A couple of our developers, which are Microsoft VB developers, are
> complaining about not being able to use proprietary MS stuff with
> PostgreSQL.
Dear Dale,
Maybe you could consider using pgAdmin2 (http://pgadmin.postgresql.org),
which d
In latest CVS:
template1=# create table test (a int4 not null);
CREATE DOMAIN
template1=#
Chris
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Well,
Someone just dropped the DROP DATABASE statement rules right in the
middle of the CREATE DATABASE production rules!!!
Fernando
Fernando Nasser wrote:
>
> The OWNER production rules added to DROP DATABASE:
>
> DropdbStmt: DROP DATABASE database_name
>
66 matches
Mail list logo
