> 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
On Fri, 2002-09-06 at 07:37, Curt Sampson wrote:
> On 5 Sep 2002, Hannu Krosing wrote:
>
> > Suppose you have a table CITIZEN with table-level constraint IS_GOOD
> > which is defined as kills_not_others(CITIZEN). and there is table
> > CIVIL_SERVANT (..) UNDER CITIZEN. Now you have just one table
Hello!
On Fri, 6 Sep 2002, Christopher Kings-Lynne wrote:
> This question should not be posted to -patches, changed accordingly.
>
> What happens if you go 'VACUUM VERBOSE FULL goods;'?
Oh, big thanx!
But 'VACUUM VERBOSE FULL goods;' didn't work, only 'VACUUM FULL VERBOSE
goods;' did.:)
I make
* Achmad Amin <[EMAIL PROTECTED]> [2002-09-05 22:54 -0700]:
> Dear all,
> I want to make library for visual basic to connect to
> PostgreSQL, but I have problem to get libpq.dll source
> code. Can somebody help me ?
Download a PostgreSQL source distribution. The libpq sources are in
src/interface
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
On Thu, 5 Sep 2002, Jeff Davis wrote:
> But a person is-a employee (allow me to momentarily step aside from
> the rules of english grammer, if you would), and a person is-a
> programmer. That's why I didn't call my table "job" :) [1]
Certainly it's not the case that a person is-a job, by virtue
Dear all,
I want to make library for visual basic to connect to
PostgreSQL, but I have problem to get libpq.dll source
code. Can somebody help me ?
(Sorry for bad english :))
Best Regards,
Achmad Amin
__
Do You Yahoo!?
Yahoo! Finance - Get real-tim
On 5 Sep 2002, Greg Copeland wrote:
> Sounds like a mechanism to make the distinction between virtual (child
> can override parent) and non-virtual (child is constrained by the
> parent) constraints are needed.
Oh, I should mention that I have no problem with being able to declare a
constraint "
On 5 Sep 2002, Hannu Krosing wrote:
> Suppose you have a table CITIZEN with table-level constraint IS_GOOD
> which is defined as kills_not_others(CITIZEN). and there is table
> CIVIL_SERVANT (..) UNDER CITIZEN. Now you have just one table MILITARY
> (...) UNDER CIVIL_SERVANT, where you have other
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
There also seems to be a more complete list of english stopwords here:
http://www.dcs.gla.ac.uk/idom/ir_resources/linguistic_utils/
However this list again does not include contractions. I can take this
list, check it and submit it to you Oleg, but do you want me to add
contractions?
eg. wasn'
> 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
> 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
Feel free to add to it. It's creation was primarily to get Autodoc to
work with my old 7.2 structures.
- Needs to handle mixed case / quoted element names (UNIQUE keys
especially).
- Deferred foreign key constraints.
I use neither, so I'm not overly worried about either unless I get a
bunch of
On Thu, 5 Sep 2002, Bruce Momjian wrote:
> I haven't see the beta announcement on the announce list. Do we
> announce it there?
I've been expecting it but haven't seen it yet.
Vince.
--
==
Vince Vielhaber -- KA8CSHema
I haven't see the beta announcement on the announce list. Do we
announce it there?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.
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
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...
>
>
>
On Thu, 2002-09-05 at 15:16, Larry Rosenman wrote:
> On Wed, 2002-09-04 at 19:41, Larry Rosenman wrote:
> > On Wed, 2002-09-04 at 17:54, Tom Lane wrote:
> > > Larry Rosenman <[EMAIL PROTECTED]> writes:
> > > > I upgraded PostgreSQL to 7.2.1 from a 7.2beta (yeah, I know). One of my
> > > > users r
> 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
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Is there a TODO here?
I've committed a fix for the immediate problem. I want to take a very
hard look at the other heap_mark4update calls, though.
regards, tom lane
---(end of broadcast)
> GNU gettext does its own encoding conversion. It reads the program's
> character encoding from the LC_CTYPE locale and converts the material in
> the translation catalogs on the fly for output. This is great in general,
> really, but for the postmaster it's a problem. If LC_CTYPE is fixed for
Gavin Sherry wrote:
> On Thu, 5 Sep 2002, Tom Lane wrote:
>
> > Gavin Sherry <[EMAIL PROTECTED]> writes:
> > > Since the flawed code is now in beta, it will need to be fixed. Do people
> > > like the above solution or should I just revert to having a seperate
> > > function for each GUC variable
Is there a TODO here?
---
Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > The following happens in latest CVS and a fresh database:
> > create table test (a int);
> > insert into test values (1);
> > alte
On Thu, 5 Sep 2002, Tom Lane wrote:
> Gavin Sherry <[EMAIL PROTECTED]> writes:
> > Since the flawed code is now in beta, it will need to be fixed. Do people
> > like the above solution or should I just revert to having a seperate
> > function for each GUC variable affected?
>
> I do not see a go
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> The following happens in latest CVS and a fresh database:
> create table test (a int);
> insert into test values (1);
> alter table test add column b text check (b <> '');
This bug's been there awhile I fear. The failure occurs when
AlterTableAddCol
On Thu, 5 Sep 2002, Stephan Szabo wrote:
>
> On Thu, 5 Sep 2002, Peter Eisentraut wrote:
>
> > The following happens in latest CVS and a fresh database:
> >
> > create table test (a int);
> > insert into test values (1);
> > alter table test add column b text check (b <> '');
> > alter table te
On Fri, 2002-09-06 at 03:14, Marc G. Fournier wrote:
> 0On Thu, 5 Sep 2002, Tom Lane wrote:
>
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > OK, so if base isn't compilable, then what is it good for? I don't see
> > > any add-on packages that would make it usable.
> >
> > AFAIR, the only re
On Fri, 2002-09-06 at 03:19, Greg Copeland wrote:
> On Thu, 2002-09-05 at 08:15, Hannu Krosing wrote:
> > On Thu, 2002-09-05 at 11:34, Curt Sampson wrote:
> > > On 5 Sep 2002, Hannu Krosing wrote:
>
> > > If that
> > > trigger is acting as an integrety constraint on the base table,
> > > you migh
On Thu, 5 Sep 2002, Peter Eisentraut wrote:
> The following happens in latest CVS and a fresh database:
>
> create table test (a int);
> insert into test values (1);
> alter table test add column b text check (b <> '');
> alter table test add check (a > 0);
> alter table test add check (a <> 1);
On Thu, 2002-09-05 at 08:15, Hannu Krosing wrote:
> On Thu, 2002-09-05 at 11:34, Curt Sampson wrote:
> > On 5 Sep 2002, Hannu Krosing wrote:
> > If that
> > trigger is acting as an integrety constraint on the base table,
> > you might destroy the table's integrity.
>
> What I try to say is that
Marc G. Fournier wrote:
> 0On Thu, 5 Sep 2002, Tom Lane wrote:
>
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > OK, so if base isn't compilable, then what is it good for? I don't see
> > > any add-on packages that would make it usable.
> >
> > AFAIR, the only reason for having the split pac
On Thu, 5 Sep 2002, Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > OK, so if base isn't compilable, then what is it good for? I don't see
> > > any add-on packages that would make it usable.
> >
> > AFAIR, the only reason for having the split packaging
0On Thu, 5 Sep 2002, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > OK, so if base isn't compilable, then what is it good for? I don't see
> > any add-on packages that would make it usable.
>
> AFAIR, the only reason for having the split packaging is to accommodate
> people who
I have removed PGPASSWORDFILE in CVS and therefore in beta2.
It was decided that $HOME/.pgpass should always be tested, rather than
have an environment variable for it.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+
Tatsuo Ishii writes:
> BTW, nls has same problem as above, no? I guess nls depeneds on locale
> and it may conflict with the database-specific encoding and/or the
> automatic FE/BE encoding conversion.
GNU gettext does its own encoding conversion. It reads the program's
character encoding from
The following happens in latest CVS and a fresh database:
create table test (a int);
insert into test values (1);
alter table test add column b text check (b <> '');
alter table test add check (a > 0);
alter table test add check (a <> 1);
After the last command I get
ERROR: CheckConstraintFetc
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > OK, so if base isn't compilable, then what is it good for? I don't see
> > any add-on packages that would make it usable.
>
> AFAIR, the only reason for having the split packaging is to accommodate
> people who are downloading acros
On Wed, 2002-09-04 at 19:41, Larry Rosenman wrote:
> On Wed, 2002-09-04 at 17:54, Tom Lane wrote:
> > Larry Rosenman <[EMAIL PROTECTED]> writes:
> > > I upgraded PostgreSQL to 7.2.1 from a 7.2beta (yeah, I know). One of my
> > > users requested plperl, so I got it to createlang, but it SIGSEGV's
Bruce Momjian <[EMAIL PROTECTED]> writes:
> OK, so if base isn't compilable, then what is it good for? I don't see
> any add-on packages that would make it usable.
AFAIR, the only reason for having the split packaging is to accommodate
people who are downloading across flaky connections --- less
Peter,
On Thu, Sep 05, 2002 at 02:51:31PM -0400, Bruce Momjian wrote:
> Jason Tishler wrote:
> > On Thu, Sep 05, 2002 at 08:33:20PM +0200, Peter Eisentraut wrote:
> > > Should all be fixed now.
> >
> > Huh? I don't see any recent CVS commits to indicate this.
>
> I see as a commit:
>
> [snip]
Just in time for 7.3 beta 1 :
http://dsc.discovery.com/news/briefs/20020902/elephant.html
---
Hannu
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
Peter Eisentraut wrote:
> Marc G. Fournier writes:
>
> > Scary, even with removing a load of stuff over to gborg, its still gotten
> > bigger then the last release :)
>
> Not hard to find the culprit:
>
> 7.2:
>
> 3.4Msrc/backend/utils/mb
>
> 7.3:
>
> 9.6Msrc/backend/utils/mb
Wow.
Jason Tishler wrote:
> Peter,
>
> On Thu, Sep 05, 2002 at 08:33:20PM +0200, Peter Eisentraut wrote:
> > Dave Page writes:
> >
> > > I get the following error when building beta 1 on CYGWIN_NT-5.1 PC9
> > > 1.3.10(0.51/3/2) 2002-02-25 11:14 i686 unknown:
> >
> > Should all be fixed now.
>
> Huh
Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > Hrmm ... that is odd, now that you mention it ... but the file
> > 'distributions' between v7.2 and v7.3beta appear to be the same, so -base-
> > was broken in the old one too?
>
> It was never intended that the "base" tarfile w
Peter,
On Thu, Sep 05, 2002 at 08:33:20PM +0200, Peter Eisentraut wrote:
> Dave Page writes:
>
> > I get the following error when building beta 1 on CYGWIN_NT-5.1 PC9
> > 1.3.10(0.51/3/2) 2002-02-25 11:14 i686 unknown:
>
> Should all be fixed now.
Huh? I don't see any recent CVS commits to in
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> Hrmm ... that is odd, now that you mention it ... but the file
> 'distributions' between v7.2 and v7.3beta appear to be the same, so -base-
> was broken in the old one too?
It was never intended that the "base" tarfile was alone sufficient to do
an
Joe Conway writes:
> I just tried to build all of contrib, and it stops at earthdistance.
Whoops...
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Dave Page writes:
> I get the following error when building beta 1 on CYGWIN_NT-5.1 PC9
> 1.3.10(0.51/3/2) 2002-02-25 11:14 i686 unknown:
Should all be fixed now.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'ki
Marc G. Fournier writes:
> Scary, even with removing a load of stuff over to gborg, its still gotten
> bigger then the last release :)
Not hard to find the culprit:
7.2:
3.4Msrc/backend/utils/mb
7.3:
9.6Msrc/backend/utils/mb
--
Peter Eisentraut [EMAIL PROTECTED]
---
Bruce Momjian writes:
> I am confused. Are you saying the base file isn't compilable?
The mb stuff is missing because it used to be optional in the old
splitting scheme. Needs to be rethought.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)
On Thu, 5 Sep 2002, Bruce Momjian wrote:
> Marc G. Fournier wrote:
> > On 5 Sep 2002, Manuel Sugawara wrote:
> >
> > > Tom Lane <[EMAIL PROTECTED]> writes:
> > >
> > > > So it would seem. The utils/mb directory is certainly there in the full
> > > > tarball that I pulled from ftp.us.postgresql.o
Bruce Momjian <[EMAIL PROTECTED]> writes:
> > You need either the 7.3b1.tar.gz (which is everything), or you need to get
> > all the various -*- parts (which are more manageable)
>
> I am confused. Are you saying the base file isn't compilable?
My idea was that it is.
Regards,
Manuel.
--
On Thu, 2002-09-05 at 20:12, Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > Good question. As far as lines of *.[chy] code in pgsql/src, you have:
> >
> > >Date | Release | Lines of code
> > > --+--+
Marc G. Fournier wrote:
> On 5 Sep 2002, Manuel Sugawara wrote:
>
> > Tom Lane <[EMAIL PROTECTED]> writes:
> >
> > > So it would seem. The utils/mb directory is certainly there in the full
> > > tarball that I pulled from ftp.us.postgresql.org this morning. How did
> > > you acquire your source
On Thu, 5 Sep 2002, Martin Porter wrote:
>
> Oleg,
>
> The Porter stemming stems herring and herrings to her, which is a bit
> unfortunate. A quick fix is to put 'herring/herrings' in the exception list
> in the english (porter2) stemmer, but I'll look at this case over the next
> few days and se
On Thu, 2002-09-05 at 19:23, Tom Lane wrote:
> I really like Hannu's idea of storing an entire (single-inheritance)
> hierarchy in a single file.
>
> I guess the question we need to ask ourselves is if we're prepared to
> abandon support of multiple inheritance. Personally I am, but...
So am I,
I'm suspecting that something blocks mail from my home computer
This is sent to test if it is so.
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
On Thu, Sep 05, 2002 at 10:23:02AM -0400, Tom Lane wrote:
> I really like Hannu's idea of storing an entire (single-inheritance)
> hierarchy in a single file.
Wouldn't this require solving the ALTER TABLE ADD COLUMN (to parent)
column ordering problem?
> I guess the question we need to ask ours
On Thu, 5 Sep 2002, Bruce Momjian wrote:
> Vince Vielhaber wrote:
> > On Thu, 5 Sep 2002, Bruce Momjian wrote:
> >
> > > Vince Vielhaber wrote:
> > > > On Thu, 5 Sep 2002, Bruce Momjian wrote:
> > > >
> > > > >
> > > > > I will work on that this month. It is part of the advocacy project.
> > > >
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> You need either the 7.3b1.tar.gz (which is everything), or you need to get
> all the various -*- parts (which are more manageable)
Oh, well. Thanks
Regards,
Manuel.
--
No es que no puedan hallar la solución: es que no ven el problema.
G.K. Chest
On 5 Sep 2002, Manuel Sugawara wrote:
> Tom Lane <[EMAIL PROTECTED]> writes:
>
> > So it would seem. The utils/mb directory is certainly there in the full
> > tarball that I pulled from ftp.us.postgresql.org this morning. How did
> > you acquire your source tree, exactly?
>
> The file is postgr
Tom Lane <[EMAIL PROTECTED]> writes:
> So it would seem. The utils/mb directory is certainly there in the full
> tarball that I pulled from ftp.us.postgresql.org this morning. How did
> you acquire your source tree, exactly?
The file is postgresql-base-7.3b1.tar.gz from
ftp://ftp.postgresql.or
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > of course I don't think a fatal or panic ever makes it
> > to the client side.
>
> Of course it does. Try entering a bad password as a trivial example.
> We punt *after* we send the elog.
Oh, that's good. I guess it was PANIC I as
Vince Vielhaber wrote:
> On Thu, 5 Sep 2002, Bruce Momjian wrote:
>
> > Vince Vielhaber wrote:
> > > On Thu, 5 Sep 2002, Bruce Momjian wrote:
> > >
> > > >
> > > > I will work on that this month. It is part of the advocacy project.
> > >
> > > Since when?
> >
> > Since I decide to take over the
In the process of upgrading a few systems for the Beta, I ended up
writing a tool to upgrade the Foreign key, Unique, and Serial objects to
their 7.3 version from the 7.2 version (may work on prior -- but not
guarenteed).
I imagine it'll fail miserably on mixed case, or names with spaces --
but o
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Is this item completed? It sure looks like it:
> > * Make triggers refer to columns by number, not name
>
> It is not necessary anymore. The triggers still use names, but there's
> code in ALTER...RENAME to fix the trigger para
Manuel Sugawara <[EMAIL PROTECTED]> writes:
> or I'm missing something?
So it would seem. The utils/mb directory is certainly there in the full
tarball that I pulled from ftp.us.postgresql.org this morning. How did
you acquire your source tree, exactly?
regards, tom lan
Oleg,
The Porter stemming stems herring and herrings to her, which is a bit
unfortunate. A quick fix is to put 'herring/herrings' in the exception list
in the english (porter2) stemmer, but I'll look at this case over the next
few days and see if I can come up with something a bit better.
Inter
How about counting the number of dead tuples examined and the number of live
tuples returned. As the ratio of dead tuples over live tuples visited
increases the table becomes a candidate for vacuuming.
-regards
richt
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECT
On Thu, 2002-09-05 at 11:19, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > SunOS control.shared2 5.7 Generic_106541-20 sun4u sparc SUNW,Ultra-5_10
> > shows an error in ALTER TABLE tests:
>
> > ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1) references
> > pktable(ptest1);
> > NOTI
On Thu, 5 Sep 2002, Bruce Momjian wrote:
> Vince Vielhaber wrote:
> > On Thu, 5 Sep 2002, Bruce Momjian wrote:
> >
> > >
> > > I will work on that this month. It is part of the advocacy project.
> >
> > Since when?
>
> Since I decide to take over the world. :-)
>
> What I meant was that it was
Vince Vielhaber wrote:
> On Thu, 5 Sep 2002, Bruce Momjian wrote:
>
> >
> > I will work on that this month. It is part of the advocacy project.
>
> Since when?
Since I decide to take over the world. :-)
What I meant was that it was on my TODO list as part of advocacy stuff I
plan for Septemb
Bruce Momjian <[EMAIL PROTECTED]> writes:
> of course I don't think a fatal or panic ever makes it
> to the client side.
Of course it does. Try entering a bad password as a trivial example.
We punt *after* we send the elog.
regards, tom lane
---(
Guys,
postgresql7.3b1 does not build :-(, seems like a missing multibyte
directory
'
| make[4]: Entering directory
|`/home/masm/download/postgresql-7.3b1/src/backend/utils/time'
| gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -I../../../../sr
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > But the client side doesn't make any sense to support FATAL. Am I
> > missing something?
>
> Hm. I suppose a client setting above ERROR might break some application
> programs that expect either ERROR or a command-complete response
Bruce Momjian <[EMAIL PROTECTED]> writes:
> But the client side doesn't make any sense to support FATAL. Am I
> missing something?
Hm. I suppose a client setting above ERROR might break some application
programs that expect either ERROR or a command-complete response ...
but do we need to go ou
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> I do not see a good reason why "fatal" and "off" shouldn't be allowed
> >> values for all three message variables. If we just did that, then you'd
> >> be back to sharable code.
>
> > I recommended he only allow valid values for ea
> -Original Message-
> From: Jason Tishler [mailto:[EMAIL PROTECTED]]
> Sent: 05 September 2002 16:30
> To: Dave Page
> Cc: pgsql-hackers; pgsql-cygwin
> Subject: Re: [CYGWIN] 7.3 Beta 1 Build Error on Cygwin
>
>
> I just submitted a patch to pgsql-patches to fix the above
> and to a
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> I do not see a good reason why "fatal" and "off" shouldn't be allowed
>> values for all three message variables. If we just did that, then you'd
>> be back to sharable code.
> I recommended he only allow valid values for each variable. I think if
> w
Dave,
On Thu, Sep 05, 2002 at 12:54:50PM +0100, Dave Page wrote:
> I get the following error when building beta 1 on CYGWIN_NT-5.1 PC9
> 1.3.10(0.51/3/2) 2002-02-25 11:14 i686 unknown:
>
> make[3]: Entering directory
>`/usr/local/src/postgresql-7.3b1/src/backend/utils/mb/conversion_procs/cyrill
Tom Lane wrote:
> There's some value in being able to kick the log level up a notch for
> a specific session, but knocking it down from the admin's default could
> be considered a bad thing. I suppose we could invent a PGC_SIGHUP
> "min_server_min_messages" variable that sets a minimum value belo
Tom Lane wrote:
> Gavin Sherry <[EMAIL PROTECTED]> writes:
> > Since the flawed code is now in beta, it will need to be fixed. Do people
> > like the above solution or should I just revert to having a seperate
> > function for each GUC variable affected?
>
> I do not see a good reason why "fatal"
Rod Taylor <[EMAIL PROTECTED]> writes:
> SunOS control.shared2 5.7 Generic_106541-20 sun4u sparc SUNW,Ultra-5_10
> shows an error in ALTER TABLE tests:
> ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1) references
> pktable(ptest1);
> NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIG
Hannu Krosing wrote:
> It seems that my last mail on this did not get through to the list ;(
>
> Please consider renaming the new builtin function
>
> split(text,text,int)
>
> to something else, perhaps
>
> split_part(text,text,int)
>
> (like date_part)
>
> The reason for this request i
Tom Lane wrote:
> 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 |
On Wed, 2002-09-04 at 22:39, Marc G. Fournier wrote:
>
> will announce it on -announce tomorrow, if ppl want to take a quick look
> at it ... man pages weren't included, but I did regenerate the docs per
> Peter's suggested commands ...
'./configure && make check' passes on i386 FreeBSD.
SunOS
I really like Hannu's idea of storing an entire (single-inheritance)
hierarchy in a single file.
I guess the question we need to ask ourselves is if we're prepared to
abandon support of multiple inheritance. Personally I am, but...
regards, tom lane
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> actually, should be a symlink, but until I know the packaging and all is
> well, I'm avoiding put it in there ...
I pulled down the main tarball -- looks good AFAICT.
regards, tom lane
---(end of br
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
>
Scott Shattuck <[EMAIL PROTECTED]> writes:
> ...why don't they allow the selects to read through adding a
> constraint?
Hmm. We could probably allow that --- at least for some forms of
ALTER TABLE, a ShareRowExclusive lock ought to be good enough.
(That would allow SELECT and SELECT FOR UPDATE t
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Is this item completed? It sure looks like it:
> * Make triggers refer to columns by number, not name
It is not necessary anymore. The triggers still use names, but there's
code in ALTER...RENAME to fix the trigger parameters. I'm perfectly
hap
Gavin Sherry <[EMAIL PROTECTED]> writes:
> Since the flawed code is now in beta, it will need to be fixed. Do people
> like the above solution or should I just revert to having a seperate
> function for each GUC variable affected?
I do not see a good reason why "fatal" and "off" shouldn't be allo
On Thu, 2002-09-05 at 12:29, Jeff Davis wrote:
> >
> > This is not so wrong. If you think about it, you have the same
> > problem in most object-oriented programming languages: a person
> > object can't generally easily become a subclass of itself after
> > being created.
> >
> > This is a case, I
On Thu, 5 Sep 2002, Marc G. Fournier wrote:
> On Thu, 5 Sep 2002, Vince Vielhaber wrote:
>
> > On Wed, 4 Sep 2002, Marc G. Fournier wrote:
> >
> > > %ls -lt ~ftp/pub/source/v7.3beta
> >
> > Is this where you're putting it this time? Last time was ~ftp/pub/beta.
>
> actually, should be a symlink,
On Thu, 5 Sep 2002, Vince Vielhaber wrote:
> On Wed, 4 Sep 2002, Marc G. Fournier wrote:
>
> > %ls -lt ~ftp/pub/source/v7.3beta
>
> Is this where you're putting it this time? Last time was ~ftp/pub/beta.
actually, should be a symlink, but until I know the packaging and all is
well, I'm avoiding
On Thu, 2002-09-05 at 11:34, Curt Sampson wrote:
> On 5 Sep 2002, Hannu Krosing wrote:
>
> > > Oh, I see. Not that this is that big a deal, I think. Given that
> > > it doesn't work correctly at the moment, making it work fast is a
> > > definite second priority, I would think.
> >
> > But choosi
I get the following error when building beta 1 on CYGWIN_NT-5.1 PC9
1.3.10(0.51/3/2) 2002-02-25 11:14 i686 unknown:
make[3]: Entering directory
`/usr/local/src/postgresql-7.3b1/src/backend/utils/mb/conversion_procs/c
yrillic_and_mic'
gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations
-I..
>
> This is not so wrong. If you think about it, you have the same
> problem in most object-oriented programming languages: a person
> object can't generally easily become a subclass of itself after
> being created.
>
> This is a case, I would say, where you simply don't want to use
> inheritance.
On Thu, 5 Sep 2002, Bruce Momjian wrote:
>
> I will work on that this month. It is part of the advocacy project.
Since when?
>
>
> ---
>
> Christopher Kings-Lynne wrote:
> > Anyone else think we should add some more pins
1 - 100 of 111 matches
Mail list logo
