> o -ALTER TABLE ADD PRIMARY KEY (Tom)
> o -ALTER TABLE ADD UNIQUE (Tom)
>
> AFAIR, I didn't do either of those; I think Chris K-L gets the credit.
Actually, I did ADD UNIQUE originally after lots of coding and then you went
and made it work by changing a couple of lines in the gramma
Looks like we got an honourable mention *sigh*:
Server Appliance: SnapGear for Lite/Lite+ SOHO Firewall/VPN Client
Honorable Mention: Sun Microsystems for Cobalt Qube
Security Tool: GPG
Web Server: IBM for xSeries
Honorable Mention: Sun Microsystems for Cobalt RaQ XRT
Enterprise Application Serve
> On Tue, 3 Sep 2002, Christopher Kings-Lynne wrote:
>
> > Database: MySQL Honorable Mention: PostgresSQL
>
> Nothing wrong with that. From your list it seemed that in the categories
> where there were competing open source and open source/commercial backed
> software t
> Actually, Linux Journal (and their editors) are fans of PostgreSQL.
>
> This year, MySQL may actually have clued in to transactions and a few
> other big database features. I don't know that they actually *have*
> these features polished up, but LJ is giving them credit for trying...
It still d
If we got rid of the other NOT NULL != CHECK (a IS NOT NULL) instance, may
as well get rid of the one on this page:
http://developer.postgresql.org/docs/postgres/sql-createdomain.html
Chris
---(end of broadcast)---
TIP 1: subscribe and unsubscrib
findoidjoins doens't seem to compile:
gmake[1]: Entering directory `/home/chriskl/pgsql-head/contrib/findoidjoins'
gcc -pipe -O -g -Wall -Wmissing-prototypes -Wmissing-declarations -I../../sr
c/interfaces/libpgeasy -I../../src/interfaces/libpq -I. -I../../src/include
-c -o findoidjoins.o findo
> Personally I would prefer to have a trigger on a metadata table
> where I could
> trigger vacuuming a particular table each n number of
> transactions(Oh it would
> be great if that vacuum runs in background not blocking meta data
> table.. just
> a wishlist...). Can anybody tell me which table
> Actually that's what I did. Update global transaction counter
> than trigger the
> vacuum from a spare thread.
>
> but having it in DB has advantages of centralisation. It's just a
> good to have
> kind of thing..
Care to submit it as a BSD licensed contrib module then? Or at least create
a p
> That brings me to another point, is there interest for this
> web-statistics-frontend, maybe for /contrib? I found it extremly useful
> because it showed up the weak points in my applications.
Why not create a project here for it: http://gborg.postgresql.org/
Chris
-
Does anyone else get this rubbish when they post to -php ?
Our domain isn't on any blacklists AFAIK...
Chris
> -Original Message-
> From: GWAVA [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, 4 September 2002 11:24 AM
> To: [EMAIL PROTECTED]
> Subject: [GWAVA:fku1fb18] Source block messag
> I have been doing some poking around with this item, and I was
> planning on
> using the stats collector to do "intelligent" auto-vacuuming. I
> was planning
> on adding some new columns that account for activity that has taken place
> since the last vacuum. The current stats collector sh
Cool. Is it worth putting it on greatbridge? gborg.postgresql.org
With the new tightening of the postgres source tree, it's unlikely this
would make it into our CVS methinks, however people are working on setting
up greatbridge as a one-stop-shop for postgres add-ons...
Chris
> -Original
Warning: Supplied argument is not a valid PostgreSQL link resource in
/usr/local/www/gborg3/html/index.php on line 52
Warning: Supplied argument is not a valid PostgreSQL link resource in
/usr/local/www/gborg3/html/include/project.php on line 196
Warning: Supplied argument is not a valid Postgr
Can someone maybe do a bit of a 'wc' on the cvs logs to see how much we've
changed between 7.2 - 7.3 compared to 7.1 - 7.2? It's evident that the
HISTORY file shows many more changes in this release than the previous, and
I think it'd be interesting to know how much/how fast postgres is gaining
m
> Hannu Krosing wrote:
> > On Thu, 2002-09-05 at 03:17, Neil Conway wrote:
> > >
> > > Tom did some work on this as well as Chris, I believe:
> > >
> > > - Add ALTER TABLE DROP COLUMN (Christopher)
> >
> > IIRC, some of it was originally based on Hiroshi's earlyer trial code,
> > so he should prob
Oleg knows about it and is planning to fix it.
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Joe Conway
> Sent: Thursday, 5 September 2002 11:55 AM
> To: pgsql-hackers
> Subject: [HACKERS] more contrib breakage
>
>
> I'm also getting a fail
Hang on - try looking at the tgargs field. I bet it still refers to fields
by their name, not their number...
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Bruce Momjian
> - CVS
> Sent: Thursday, 5 September 2002 12:58 PM
> To: [EMAIL PROT
Anyone else think we should add some more pins to the developer map? At the
moment, it looks like we have very few developers!
Chris
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregist
> * Pre-6.3 clients are no longer supported.
>
> Is that supposed to be 7.3? I assume you're referring to the
> catalog changes,
> &c. that make old clients that are dependent on them behave incorrectly.
>
> Regards,
> Jeff Davis
No, he's referring to the on-the-wire protocol. This means t
Hi Oleg/Teodor,
I'm sorry to keep posting bugs without patches, but I'm just hoping you guys
know the answer faster than I...I know you're busy.
What does tsearch have against the word 'herring' (as in the fish). Why is
it considered a stopword?
Attached is example queries...
Chris
usa=# se
dx
## 'himing';
food_id | brand | description | ftiidx
-+---+-+
(0 rows)
All work...?
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Christopher
> Kings-Lynne
> Sent: Thursday, 5 September 2002
Was this going to make it into the release notes or something?
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Tom Lane
> Sent: Tuesday, 3 September 2002 9:54 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: [HACKERS] 7.3 gotchas for
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Good question. As far as lines of *.[chy] code in pgsql/src, you have:
>
> > Date | Release | Lines of code
> > --+--+
> > ...
> > 2002-02-04 | 7.2 | 394,274
> > 200
Whoot! I was just thinking about writing such a tool. Thanks.
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Rod Taylor
> Sent: Friday, 6 September 2002 12:38 AM
> To: PostgreSQL-development
> Subject: [HACKERS] Ok, I broke down...
>
>
>
OK,
I note that the regression tests for the following contribs are failing:
cube
intarray
seg
Chris
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
> Should we check for stop words before stemming or after ?
I think you should.
> In the first case we have to collect all forms of stop-words
> which is doable
> but difficult to maintain, in latter - we'll have current problem.
Looking at the list of stopwords you sent me, Oleg, there are onl
> Looking at the list of stopwords you sent me, Oleg, there are only about 1
> out of the list of 120 stopwords that need to have all word forms
> added. I
> also don't think it'll be a maintenance problem. The reason I
> think this is
> because stopwords in general don't have different word f
. wasn't, isn't, it's, etc.?
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Christopher
> Kings-Lynne
> Sent: Friday, 6 September 2002 12:20 PM
> To: Christopher Kings-Lynne; Oleg Bartunov
> Cc: Hackers; [EMAI
OK,
The argument about using ALTER TABLE/ADD FOREIGN KEY in dumps was that it
caused an actual check of the data in the table, right? This was going to
be much slower than using CREATE CONSTRAINT TRIGGER.
So, why can't we do this in the SQL that pg_dump creates (TODO):
CREATE TABLE ...
ALTER T
Hi Yury,
This question should not be posted to -patches, changed accordingly.
What happens if you go 'VACUUM VERBOSE FULL goods;'?
Your on-disk files won't shrink or have unused tuples removed unless you
VACUUM FULL. The problem with doing VACUUM FULL is that it totally locks
the whole table w
> I make a guess I've got this due to parallel running of a program making
> bulk INSERTs/UPDATEs into that table. Mmm...I need a way to avoid the big
> number of unused pages in such a case. LOCK TABLE?
Well, I suggest doing a normal vacuum analyze ('VACUUM ANALYZE goods') after
every bulk inser
I got:
random_page_cost = 0.807018
For FreeBSD 4.4/i386
With 512MB RAM & SCSI HDD
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Bruce Momjian
> Sent: Monday, 9 September 2002 2:14 PM
> To: PostgreSQL-development
> Subject: Re: [HACKERS]
Hi Guys,
You might be interested in the results of the Australian Open Source Awards:
http://www.smh.com.au/articles/2002/09/06/1031115931961.html
Justin Clift and I both rated mentions - Justin for the Postgres websites
and myself for BSD Users Group WA.
One good things is that both Postgres
website they point to *isn't* techdocs, but www, which Justin has had
> nothing to do with ;(
>
> On Mon, 9 Sep 2002, Christopher Kings-Lynne wrote:
>
> > Hi Guys,
> >
> > You might be interested in the results of the Australian Open
> Source Awards:
> &g
Assuming it's giving out correct information, there seems to be a lot of
evidence for dropping the default random_page_cost to 1...
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Hans-Jürgen
> Schönig
> Sent: Monday, 9 September 2002 4:06 PM
Sorry guys - it's killing me! It's 'affected' in the subject line - not
'effected'!!! Sigh :)
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Bruce Momjian
> Sent: Tuesday, 10 September 2002 10:24 AM
> To: Peter Eisentraut
> Cc: Steve Howe;
I got somewhat different:
$ ./randcost /usr/local/pgsql/data
Collecting sizing information ...
Running random access timing test ...
Running sequential access timing test ...
Running null loop timing test ...
random test: 13
sequential test: 15
null timing test: 11
random_page_cost = 0.
I think it should be made. Don't force an initdb. Beta testers can run the
update. 'split' is a pretty standard function these days...
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Bruce Momjian
> Sent: Wednesday, 11 September 2002 10:33
timestamp becoming timestamp without time zone is actually the SQL
standard...
Chris
> I'm sure you all have discussed this ad-nauseum but this sure
> does create a
> pain in the butt when converting.
>
> Ok, I had my say.
>
> Thanks for all your hard work,
>
> L.
> On Wed, 11 Sep 2002, Bruce Mo
MySQL wins Prestigious Linux Journal's Editors' Choice Award:
http://www.mysql.com/news/article-109.html
An amusing quote from the article:
"If you're one of the people who has been saying, 'I can't use MySQL because
it doesn't have [feature you need here]', it's time to read up on MySQL 4.0
an
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Bruce Momjian writes:
> >> I would love to say that this is related to change in casts, but that
> >> isn't the case.
>
> > Sure it is. The float=>int casts need to be made implicit, or
> we'll have
> > tons of problems like this.
>
> Well, ye
> AFAIK, the extra index only slows down my inserts - it basically contains
> no usable information...
Not 100% true. It will speed up cascade delete and update...
> shouldn't the presence of _primary_key_ in
> multicol foreign key be enough to decide whether the whole key is unique
> or not?
> > It seems all of this discussion misses the point. Either it has a large
> > amount of impact and the idea gets rejected because of implementation
> > issues, or it has little impact but it's nothing the core group wants to
> > implement. If the problem is finding someone to implement it, it so
> I use PostgreSQL on Linux for production and XP for development, and am
> likely to continue that way. I've been beta testing the native Win32
> port of PostgreSQL as Justin has and the latest version is fantastic -
> it runs as a service, osdb shows impressive results compared to Cygwin
> Postg
> What I can't understand is the attitude of some people here. Yes,
> Microsoft are evil, but the bottom line is, millions of people use
> Windows. Just look at the number of downloads for pgAdmin (shown at
> http://www.pgadmin.org/downloads/) - the last stable version has clocked
> up over 38,000
> Let's leave it. The main point to focus postgres on unix is not
> only because
> unix is proven/known as robust and scalable, but unix is much
> more standard to
> support across multiple OS. The amount with which windows differs
> from unices
> on API level, any serious efforts to make postgres
Hi Jerome,
The RECORD type is used for writing stored procedures and functions that
return sets.
eg. CREATE FUNCTION foo() RETURNS setof adress
AS '...';
Sort of thing...
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jerome Chochon
Sent: Tuesd
> When I say that the second form of CREATE TYPE allow you to make
> RECORD type
> like RECORD, i don't want to speak about the record in PlPgsql but RECORD
> from programming language like ADA or C (typedef struct).
>
> So the real question is:
> Can I use this new type like other user-type ?
> C
> * A reloaded dump will not create dependencies between serial columns
> and sequence objects, nor between triggers and foreign key
> constraints, thus 7.3's nifty new support for DROP CONSTRAINT won't
> work, nor will dropping a table make its associated sequences go away.
> However, thi
> I just want people to not get bit in a bad way and decide they
> don't want to
> use PostgreSQL after all. And with the new features of 7.3, lots
> of users
> who might have begun with 7.2 are going to want to upgrade -- but
> if it's too
> painful Sorry, it's just a sore spot for me, this
> > How does pg_upgrade work?
>
> pg_upgrade sort of worked for 7.2 but I got to it too late and I didn't
> properly expand the pg_clog files. In 7.3, the file format has changed.
> If we don't change the format for 7.4, I can do it, but I have to add
> schema stuff to it. Shouldn't be too hard
>
> I'd give up a few extensibility features for solid upgrading. If
> I didn't
> have so much invested in PostgreSQL I might take a hard look at MySQL 4,
> since data migration has heretofore been one of their few real
> strengths.
> But I've got three years of RPM maintenance and five years of
> Sounds good. I think the earliest we could be ready for beta2 is the
> end of this week; sometime next week may be more realistic.
>
> Given that we'll be forcing an initdb for beta2 anyway, those who use
> RPMs may be just as happy to have missed beta1.
If an initdb is planned - did that spli
> I would like to inquire how is the BLOB support in
> PostgreSQL is doing
> > now? Had there been some improvements? Can I have the blob
> support like in
>
> I'm unsure about blob (didn't know we had a blob type), but bytea works
> perfectly fine for that.
Is there some reason why we didn't
> I completely agree with Bruce here. Requiring an initdb for every beta
> release significantly reduces the number of people who will be willing
> to try it out -- so initdb's between betas are not disasterous, but
> should be avoided if possible.
But it does mean that 7.3 to 7.3 pg_dump gets a
Hi,
Should someone just go though contrib/ and add GRANT EXECUTE on everything?
Seems pointless doing it ad hoc by the maintainer as it is at the moment...?
Chris
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PRO
> On Wed, Sep 18, 2002 at 08:01:42PM -0400, Bruce Momjian wrote:
>
> > Second, when you unlink() a file on Win32, do applications continue
> > accessing the old file contents if they had the file open before the
> > unlink?
>
> I'm pretty sure it errors with 'file in use'. Pretty ugly, huh?
Yeah
I just saw this in my logs:
2002-09-18 12:13:10 ERROR: cannot open segment 1 of relation users_sessions
(target block 1342198864): No such file or directory
This query caused it:
DELETE FROM users_sessions WHERE changed < ('now'::timestamp - '1440
minutes'::interval) AND name = 'fhnid';
Howe
Will the new casting stuff address this kind of annoyance?
usa=# select average(octet_length(val)) from users_sessions;
ERROR: Function 'average(int4)' does not exist
Unable to identify a function that satisfies the given argument
types
You may need to add explicit typecasts
Chr
> > DELETE FROM users_sessions WHERE changed < ('now'::timestamp - '1440
> > minutes'::interval) AND name = 'fhnid';
>
> What does EXPLAIN show as the plan for that query? I'm guessing an
> indexscan, and that the error was caused by reading a broken item
> pointer from the index. (1342198864 =
> That seems right, but the problem I have with it is that the resulting
> state of c.f1 is attisinherited = 1. This means that you cannot drop
> c.f1. It seems to me that we should have this behavior:
Has anyone given much thought as to perhaps we could just drop multiple
inheritance from Post
Doh - I'm stupid. Ignore my question :)
Helps if you spell 'average' as 'avg' :)
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Christopher
> Kings-Lynne
> Sent: Friday, 20 September 2002 10:03 AM
&
> > > I am for it. Multiple inheritance is more of a mess than a help.
> >
> > I'm not agin it ... but if that's the lay of the land then we have
> > no need to apply a last-minute catalog reformatting to fix a
> > multiple-inheritance bug. This patch is off the "must fix for 7.3"
> > list, no?
> > The decision at hand is whether to apply a patch. You cannot say "we're
> > not deciding now", because that is a decision...
>
> Yes. I am saying we should not assume we are going to remove multiple
> inheritance. We should apply the patch and make things a good as they
> can be for 7.3.
I
> > Index Scan using users_sessions_cha_name_idx on users_sessions
> > (cost=0.00..12738.07 rows=1275 width=6) (actual
> time=231.74..239.39 rows=2
> > loops=1)
> > Total runtime: 239.81 msec
> >
> > EXPLAIN
> >
> > The size of the table:
> >
> > canaveral# ls -al 44632
> > -rw--- 1 pgsql pg
> > the hardware. On the other hand I do believe I saw a message
> > recently saying that some of the 2.4 series kernels had file system
> > bugs.
>
> I recall problems, offhand, with 2.4.5, 2.4.10, 2.4.11 (which was so
> broken that you couldn't recover), and 2.4.15. I seem to recall a
> report
> >From /.
>
>
> "Ever since Oracle announced they wouldn't port 9i to NetWare, Novell
> has been scrambling to find an enterprise-capable DB. Now it looks like
> they're settling on PostgreSQL. This follows their decision to ship
> Apache as the default web server for NetWare 6. Linux aficiona
Hi Guys,
I'm heading off on a 5 week European trip tommorrow, so I'm not going to be
around until the 31st oct.
I hope there'll be a nice new release version of Postgres I can upgrade to
when I get back!
Chris
---(end of broadcast)---
TIP 5: Hav
Hi guys,
Just got back from my European vacation - 7.3 still not out? :)
Chris
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
CVS Tip:
gmake[3]: Entering directory
`/home/chriskl/pgsql-head/src/backend/bootstrap'
gcc -pipe -O -g -Wall -Wmissing-prototypes -Wmissing-declarations -I.
-I../../../src/include -c -o bootparse.o bootparse.c -MMD
In file included from bootscanner.l:43,
from bootparse.y:339:
bo
Hi,
Seems there's a few errors in the SQL99 compatibility list. For one, it
says we support WITH CHECK OPTION on views which I'm pretty sure we don't.
Also Referential MATCH types? We don't do partial I think. I think someone
might have to give the list a once-over...?
Chris
---
> > Perhaps P_MAXLEN now needs to be (2*(DBL_DIG+2+7)+1), considering
> > that we'll allow extra_float_digits to be up to 2. What's it used for?
>
> Yes. I guess so, because it is used in what I think is a memory
> allocation function. P_MAXLEN is only used twice:
Curse my slowness, but what's
Hi Oleg & Teodor,
This behaviour is causing problems in my search engine:
australia=# select 'banana/pineapple'::mquery_txt;
mquery_txt
'banana/pineapple'
(1 row)
In our case the forward slash symbol should really be treated as a word
break. Are there any cases where
> Laurette Cisneros <[EMAIL PROTECTED]> writes:
> > bison --version
> > GNU Bison version 1.28
>
> > Should I update it?
>
> Yes.
>
> It's interesting that bison 1.28's output is sufficiently different to
> cause a problem, but we are not going to worry about supporting use of
> old bisons.
Do I h
Turn
on query monitoring in the postgresql.conf and then go:
select
* from pg_stat_activity;
Chris
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Osvâneo A.
FerreiraSent: Wednesday, 6 November 2002 4:49 AMTo:
[EMAIL PROTECTED]Subject
> "Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
> > > My presumption would be that if you initialize 2 databases to
> > > a known identical start, have all the same triggers and rules
> > > on both, then send all queries to both databases, you will
> > > have 2 identical databases at the end.
> >
>
On FreeBSD/Alpha, all 89 tests pass.
I get this build warning though:
gcc -pipe -O -Wall -Wmissing-prototypes -Wmissing-declarations -I. -I../../.
./src/include -c -o gram.o gram.c
In file included from gram.y:7725:
scan.l: In function `yyerror':
scan.l:583: warning: int format, different type
Hi,
Has anyone given much thought to improving pg_dump's object order algorithm
for 7.4? It seems that now we have dependencies, it should just be a matter
of doing a breadth-first or depth-first search over the pg_depend table to
generate a valid order of oids.
To allow for mess-ups in that tab
> pg_dump already has rudimentary dependency tracking (one level
> deep); each
> item can have a list of oid's it depends on. You *could* patch it to add
> the types to the table dependencies.
>
> In the future I'd imagine we'll just dump the OIDs of all first level
> dependencies for each object,
> > We can't just wait around indefinitely for port reports that may or may
> > not ever appear. In any case, most of the "<7.3" entries in the list
> > seem to be various flavors of *BSD; I think it's unlikely we broke
> > those ...
>
> Note that we have *zero* reports for any flavor of NetBSD an
> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > FWIW, gmake check and gmake bigcheck pass on:
> > FreeBSD 3.3-RELEASE #3: Thu Feb 3 23:48:56 GMT 2000
>
> > with the expection of:
> > [snipped]
> > in the float8 test.
>
> Okay, looks like we need to use float8-fp-exception.out on your
> platfo
> The thought that I'd been toying with is to build a list of inter-object
> dependencies (using pg_depend if available, else fall back on pg_dump's
> native wit, ie, the rather limited set of dependencies it already
> understands). Then do a topological sort, preferring to maintain OID
> order in
I just came across this article:
http://newsforge.com/newsforge/02/11/11/1848223.shtml?tid=3
It's an ERP company, OpenMFG, that uses Linux, PostgreSQL and QT. In the
article they say they're active in Postgres development. Just wondering if
they wanted to say hi!
Chris
-
> After our and the pg7.3 release is out we'll port there and I
> really would like
> to get rid of this restriction with that release than. So it
> would be wonderful
> if that still goes into the final of 7.3.
I'm not a core developer, but I'll tell you right now that there's pretty
much zero ch
> Sorry, I was vague. I think we should apply and go to RC1 tomorrow.
> There will always be tweaks and fixes. If we expect it to be perfect,
> we will never make a final release. We are 2.5 months into beta, and
> if we don't want +3 months beta, we should get going.
>
> We have to start taki
> Problem is when I want change view (or functions) with a lot of
> dependecies
> I must drop and recreate all dependent views (or functions) - I
> want add only
> one column in view
> I don't know if solution hard for that.
This is definitely something that will cause some anguish in 7.3. I thin
Hi Guys,
I emailed a few people to try to get some platform reports. What was the
solution to this problem? It was AWK or something wasn't it? Will Martin
have to try RC1?
Chris
> > We are trying to get our supported platforms list together, and
> so far we
> > have not had any platform repor
> > Well, doing create or replace as a drop/create might very well
> do the same
> > thing, and even if it got the same oid, we'd have to be really sure that
> > nothing would misbehave upon receiving that extra column before allowing
> > it for purposes of avoiding recreation of dependencies.
> >
> On Sunday 10 November 2002 08:51 am, Hannu Krosing wrote:
> > snpe kirjutas L, 09.11.2002 kell 22:51:
> > > Hello,
> > > I work with JDeveloper and PostgreSQL JDBC and I have one problem.
> > > I get error :
> > > sub-SELECT in FORM must have an alias
> > > I can't change SQL command, but it
Looks pretty sweet, Neil.
Maybe you could look at column triggers while you're at it, per comment on
Compiere page ;)
Triggers
Compiere uses triggers to ensure data consistency. It seems that in general,
Oracle triggers are relatively easy to convert. In addition to the Function
issues, a proced
> Just a quick note to mention that I've resigned from the PostgreSQL
> steering committee. It has been a lot of fun and very rewarding to
> participate in PostgreSQL development over the last six years, but it is
> time to take a break and to move on to other projects.
Thanks for all your work, T
> I will reiterate for the new folks that the core group doesn't do much
> more than decide if the final release will be on a Friday or a Monday,
> and deal with private issues like discipline. I think we deal with such
> issues perhaps 2-4 times a year.
OK sorry - I was under the impression that
This is a successful report for OpenBSD 3.2 on sparc and i386
> -Original Message-
> From: bpalmer [mailto:[EMAIL PROTECTED]]
> Sent: Monday, 18 November 2002 2:14 AM
> To: Christopher Kings-Lynne
> Subject: Re: PostgreSQL 7.3 Platform Testing
>
>
> Sorry for takin
> In looking at the CLUSTER ALL patch I have applied, I am now wondering
> why the ALL keyword is used. When we do VACUUM, we don't use ALL.
> VACUUM vacuums all tables. Shouldn't' CLUSTER alone do the same thing.
> And what about REINDEX? That seems to have a different syntax from the
> other
Was there supposed to be a patch attached to this email?
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Evgen Potemkin
> Sent: Friday, 15 November 2002 5:38 PM
> To: [EMAIL PROTECTED]
> Subject: [HACKERS] Proposal of hierarchical queries, a l
> Ports list updated:
Sure? Still says 7.2 for openbsd and has old submission date...
> http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Hi Neil,
> However, the FreeBSD box I'm playing with isn't mine, so I'm not too
> keen to change sysctls (well, that and I don't have root :-) ). Would
> a kind BSD user confirm that:
>
> (a) the sysctls above *can* be used to change kernel shared
> memory settings, and the def
> > Are those two syntaxes eqivalent ?
> >
> > select * from users where monitored;
> > select * from users where monitored=true;
> >
> > If the answer is yes, the optimimer probably doesn't agree with you :)
>
> That depends on the definition of equivalent. They presumably give the
> same answer
> > I think his point is that they _should_ be equivalent. Surely there's
> > something in the optimiser that discards '=true' stuff, like 'a=a'
should be
> > discarded?
>
> I figure that's what he meant, but it isn't what was said. ;)
>
> "col" isn't of the general form "indexkey op constant" or
> > Not that I see the point of indexing booleans, but hey :)
>
> If one of the values is much more infrequent than the other, you can
> probably get a substantial win using a partial index, can't you?
Yes, I thought of the partial index after I wrote that email :)
Chris
-
301 - 400 of 2140 matches
Mail list logo
