- Original Message -
From: "Sean Chittenden" <[EMAIL PROTECTED]>
To: "Tom Lane" <[EMAIL PROTECTED]>
Cc: "Andrew Dunstan" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, October 28, 2003 7:59 PM
Subject: Re: [HACKERS] pg_ctl reports succes when start fails
> > > We can also try t
Sean Chittenden wrote:
> > > We can also try to come up with a better scheme for verifying that
> > > we have started properly - I will think about that.
> >
> > There have been previous suggestions for a "pg_ping" functionality,
> > in which you could simply send a packet to the postmaster and it
On Tue, 2003-10-28 at 19:34, scott.marlowe wrote:
> On Tue, 28 Oct 2003, Tom Lane wrote:
>
> > "scott.marlowe" <[EMAIL PROTECTED]> writes:
> > > Is it possible to remove the implicit search path of pg_catalog from a
> > > psql session without it breaking lots of stuff?
> >
> > Do you consider "+
AFAICT there was no discussion about this issue when the patch was
proposed and applied. But now that the point is raised I have to say
that I don't like this change. I don't think system catalogs should be
excluded from tab completion. They never were before 7.4, and I have
not seen anyone com
OK, doesn't look like we are going to add the ability to turn off
constraint checking for reload, nor add ANALYZE as part of ALTER TABLE
ADD FOREIGN KEY, so we only have a few items left.
Hey - what about if you just delete the pg_constraint entries for all
your foreign keys, then won't they all b
> > Certainly other alpha gcc platforms must have problems with -O2?
> > I am inclined to add something to configure.in for all alpha
> > compiles that changes -O2 to -O.
>
> I'm not. It's one thing if FreeBSD thinks their compiler is broken.
> But before I accept that gcc is broken as a whole, I
> > We can also try to come up with a better scheme for verifying that
> > we have started properly - I will think about that.
>
> There have been previous suggestions for a "pg_ping" functionality,
> in which you could simply send a packet to the postmaster and it
> would answer back if it's open
On Tue, 28 Oct 2003, Tom Lane wrote:
> "scott.marlowe" <[EMAIL PROTECTED]> writes:
> > Is it possible to remove the implicit search path of pg_catalog from a
> > psql session without it breaking lots of stuff?
>
> Do you consider "+", "count()", etc to be important stuff?
Me, hardly ever use th
Johan Henselmans <[EMAIL PROTECTED]> writes:
> I had trouble compiling postgressrc/pgsql/src/interfaces/ecpg/ecpglib
> and compiling pgsql/src/interfaces/ecpg/compatlib.
> Reason was I had asked during configure to include krb5 support. After
> adding the -lkrb5 flag to the Makefile in these s
"scott.marlowe" <[EMAIL PROTECTED]> writes:
> Is it possible to remove the implicit search path of pg_catalog from a
> psql session without it breaking lots of stuff?
Do you consider "+", "count()", etc to be important stuff?
regards, tom lane
---
On Tue, 2003-10-28 at 18:49, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > I say leave it the way it is. If you want system table tab completion,
> > simply:
> > ALTER USER ... SET search_path =3D pg_catalog,...;
>
> Unfortunately, that *does not* affect the tab-completion b
On Tue, 28 Oct 2003, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > I say leave it the way it is. If you want system table tab completion,
> > simply:
> > ALTER USER ... SET search_path =3D pg_catalog,...;
>
> Unfortunately, that *does not* affect the tab-completion behavior
On Mon, 2003-10-27 at 10:05, Neil Conway wrote:
> On Sun, 2003-10-26 at 17:24, Oliver Elphick wrote:
> > If it were possible to have two separate versions of the PostgreSQL
> > packages installed simultaneously, it would be simple to do database
> > upgrades by dumping from the old version and uplo
Rod Taylor <[EMAIL PROTECTED]> writes:
> I say leave it the way it is. If you want system table tab completion,
> simply:
> ALTER USER ... SET search_path =3D pg_catalog,...;
Unfortunately, that *does not* affect the tab-completion behavior;
it will still not offer the system catalogs as c
Ian Barwick <[EMAIL PROTECTED]> writes:
> On Tuesday 28 October 2003 23:47, Tom Lane wrote:
>> Another odd thing was that after completing "pg_catalog.", it
>> wouldn't go any further --- one must type "p" here, even though all the
>> possible completions begin "pg_". (Possibly that could be fixed
> Anyway, it seems like we need a vote to see how many people prefer
> each choice.
I say leave it the way it is. If you want system table tab completion,
simply:
ALTER USER ... SET search_path = pg_catalog,...;
I would like to see the information_schema be a part of the default
search_p
On Tuesday 28 October 2003 23:47, Tom Lane wrote:
> Alvaro Herrera Munoz <[EMAIL PROTECTED]> writes:
> > I found it very irritating at first, but when I discovered that I could
> > tab my way to syscatalogs by using "pg_catalog." as prefix, I started
> > feeling it was actually a nice behavior.
>
>
Greg Stark <[EMAIL PROTECTED]> writes:
> I think I'm missing something. Why are pg_catalog.* tables in my search path
> at all? My search path seems to be set to $user,public. is pg_catalog
> implicitly appended there?
Yes. See TFM:
http://developer.postgresql.org/docs/postgres/ddl-schemas.html
p
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> 2. include catalog objects in expansion iff we are expanding "pg_" +
> optional suffix (probably best of both worlds).
Hmm, that might be an okay compromise. Not sure how hard it is to
implement ...
regards, tom lane
Alvaro Herrera Munoz wrote:
On Tue, Oct 28, 2003 at 04:48:59PM -0500, Tom Lane wrote:
AFAICT there was no discussion about this issue when the patch was
proposed and applied. But now that the point is raised I have to say
that I don't like this change. I don't think system catalogs should be
excl
Alvaro Herrera Munoz <[EMAIL PROTECTED]> writes:
> I found it very irritating at first, but when I discovered that I could
> tab my way to syscatalogs by using "pg_catalog." as prefix, I started
> feeling it was actually a nice behavior.
Hm. Okay, Ian isn't completely alone then ;-)
I tried out
I think I'm missing something. Why are pg_catalog.* tables in my search path
at all? My search path seems to be set to $user,public. is pg_catalog
implicitly appended there?
--
greg
---(end of broadcast)---
TIP 3: if posting/reading through Usene
On Tue, Oct 28, 2003 at 04:48:59PM -0500, Tom Lane wrote:
> AFAICT there was no discussion about this issue when the patch was
> proposed and applied. But now that the point is raised I have to say
> that I don't like this change. I don't think system catalogs should be
> excluded from tab compl
Tom Lane wrote:
Gaetano Mendola <[EMAIL PROTECTED]> writes:
I'm esperiencing problem with the autocomplete on
postgres 7.4beta5:
#select * from pg_l
and no suggestions out.
This appears to have been a deliberate change:
2003-03-27 11:45 momjian
* src/bin/psql/tab-comple
On Tuesday 28 October 2003 22:48, Tom Lane wrote:
> AFAICT there was no discussion about this issue when the patch was
> proposed and applied. But now that the point is raised I have to say
> that I don't like this change. I don't think system catalogs should be
> excluded from tab completion.
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> AFAICT there was no discussion about this issue when the patch was
>> proposed and applied. But now that the point is raised I have to say
>> that I don't like this change. I don't think system catalogs should be
>> excluded from tab
On Tue, 28 Oct 2003, Tom Lane wrote:
> Note that tables, indexes, views and sequences relations in the
> 'pg_catalog' namespace are excluded even though they are in the
> current search path. I found not doing this produced annoying
> behaviour when expanding names beginnin
Tom Lane wrote:
> This appears to have been a deliberate change:
>
> 2003-03-27 11:45 momjian
>
> * src/bin/psql/tab-complete.c: Attached are two patches for psql's
> tab-completion.c.
> [snip]
>
> Note that tables, indexes, views and sequences relations in the
>
Gaetano Mendola <[EMAIL PROTECTED]> writes:
> I'm esperiencing problem with the autocomplete on
> postgres 7.4beta5:
> #select * from pg_l
> and no suggestions out.
This appears to have been a deliberate change:
2003-03-27 11:45 momjian
* src/bin/psql/tab-complete.c: Attached are two
Steve Crawford <[EMAIL PROTECTED]> writes:
> The psql help for copy (version=7.3.2 and several others) appears
> incorrect (or perhaps the command parser is at fault - in any case
> the help doesn't match reality):
You seem to be confusing the SQL command COPY with the psql command \copy.
They a
The psql help for copy (version=7.3.2 and several others) appears
incorrect (or perhaps the command parser is at fault - in any case
the help doesn't match reality):
steve=# \h copy
Command: COPY
Description: copy data between files and tables
Syntax:
COPY table [ ( column [, ...] ) ]
FR
Jochem van Dieten <[EMAIL PROTECTED]> writes:
> Perhaps the pg_dump bug with procedural language handlers which
> have been created in the pg_catalog schema:
> http://archives.postgresql.org/pgsql-general/2003-01/msg6.php
Since no better solution has emerged since January, I've applied a patc
OK, doesn't look like we are going to add the ability to turn off
constraint checking for reload, nor add ANALYZE as part of ALTER TABLE
ADD FOREIGN KEY, so we only have a few items left.
I think we are nearing the conclusion that --enable-debug is OK now (no
-g without it), so the only remaining
Neil Conway wrote:
> On Tue, 2003-10-28 at 12:57, Bruce Momjian wrote:
> > OK, but it is going to look kind of big up there and isn't of general
> > usefulness. Still want it?
>
> Well, as a matter of principle, I think it belongs there: if it's a
> command-line option, it should be documented in
Devrim GUNDUZ <[EMAIL PROTECTED]> writes:
> On Tue, 28 Oct 2003, Robert E. Bruccoleri wrote:
>> You can build the latest release of bison from www.gnu.org
>> without any trouble under Irix.
> Is it just bison that creates the problem?
If you're working from a tarball rather than a CVS pull, you
On Tue, 2003-10-28 at 12:57, Bruce Momjian wrote:
> OK, but it is going to look kind of big up there and isn't of general
> usefulness. Still want it?
Well, as a matter of principle, I think it belongs there: if it's a
command-line option, it should be documented in the section that claims
to doc
Andrew Sullivan wrote:
On Tue, Oct 28, 2003 at 01:09:36AM -0500, Bruce Momjian wrote:
I am grouping the above two items together --- I thought the idea was to
give people a way to load 7.4 in a fairly rapid manner --- we now have
the ability to do ALTER TABLE ADD CONSTRAINT, but it lacks ANALYZE
s
Someone showed me this simple example:
regression=# CREATE TABLE test (a TEXT, b TEXT);
CREATE TABLE
regression=# INSERT INTO test VALUES ('foo', 'bar');
INSERT 17145 1
regression=# CREATE FUNCTION foo() RETURNS SETOF test as 'SELECT * FROM test' LANGUAGE
sql;
CREATE FUNCTION
regression=# SELECT
On Tue, 2003-10-28 at 11:41, Devrim GUNDUZ wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> Hi,
>
> On Tue, 28 Oct 2003, Robert E. Bruccoleri wrote:
>
> > You can build the latest release of bison from www.gnu.org
> > without any trouble under Irix.
>
> Is it just bison that
Neil Conway wrote:
> On Tue, 2003-10-28 at 10:01, Bruce Momjian wrote:
> > OK, that attached patch completes this item. I did not document
> > --describe-config at the top as an accepted arg, but there was already a
> > --name=value line.
>
> Why does '--name=value' suffice as documentation for
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Tue, 28 Oct 2003, Robert E. Bruccoleri wrote:
> You can build the latest release of bison from www.gnu.org
> without any trouble under Irix.
Is it just bison that creates the problem?
I'll try on Thursday (it's national holiday in he
On Tue, 2003-10-28 at 10:01, Bruce Momjian wrote:
> OK, that attached patch completes this item. I did not document
> --describe-config at the top as an accepted arg, but there was already a
> --name=value line.
Why does '--name=value' suffice as documentation for
'--describe-config'? I think you
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> This strikes me as a completely arbitrary set of changes in
>> long-established behavior. People who want to turn off optimization
>> already know how to do it, and people who want asserts already know
> How do you do it? CFLAGS="" c
Dear Devrim,
You can build the latest release of bison from www.gnu.org
without any trouble under Irix. PostgreSQL 7.4 builds cleanly on Irix,
and so far, it's much faster than 7.3 for the one database I've
tested. --Bob
+-++
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 8 Oct 2003, Robert E. Bruccoleri wrote:
> Dear Devrim,
> I have been using Postgres on Irix for over 8 years, and I have only
> used the SGI provided compilers. GCC doesn't work well on Irix. In addition,
> you can build a 64 bit versio
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I think I have a compromise for --enable-debug: How about if
> > --enable-debug removes optimization, adds -g (or -g3 for macro debugging
> > symbols in gcc), and maybe even enables casserts.
>
> This strikes me as a completely arbit
On Tue, Oct 28, 2003 at 01:09:36AM -0500, Bruce Momjian wrote:
> I am grouping the above two items together --- I thought the idea was to
> give people a way to load 7.4 in a fairly rapid manner --- we now have
> the ability to do ALTER TABLE ADD CONSTRAINT, but it lacks ANALYZE
> statistics, so it
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I think I have a compromise for --enable-debug: How about if
> --enable-debug removes optimization, adds -g (or -g3 for macro debugging
> symbols in gcc), and maybe even enables casserts.
This strikes me as a completely arbitrary set of changes in
long-
Tom Lane wrote:
> > Document new --describe-config postgres option
>
> Go to it.
>
OK, that attached patch completes this item. I did not document
--describe-config at the top as an accepted arg, but there was already a
--name=value line.
I added it to the bottom of the "SEMI-INTERNAL OPTIONS"
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> Basically, my question is why ::regproc alone always addes the catalogue
> qualification in this case?
regproc adds the schema if the name would be ambiguous without it (or
not visible at all). In these cases, the function name is still
ambig
Bruce Momjian wrote:
Joshua D. Drake wrote:
Hello,
Well the reason I brought it up was the rather interesting discussion
that Jan had today about Vacuum.
I was wondering if we were going to explore that before the 7.4 release?
No, I am afraid we are way past time time for that kind of addition
Bruce Momjian wrote:
> > > Have gcc use -g, add --disable-debug, rename?
> >
> > Personally I don't like the idea of this behavior defaulting differently
> > depending on which compiler you use. I can see the practical arguments
> > for doing so, but it still rubs me the wrong way. Can anyone of
On Mon, Oct 27, 2003 at 11:32:45PM -0500, Tom Lane wrote:
> > Have gcc use -g, add --disable-debug, rename?
>
> Personally I don't like the idea of this behavior defaulting differently
> depending on which compiler you use. I can see the practical arguments
> for doing so, but it still rubs me th
On Tue, 2003-10-28 at 00:02, Bruce Momjian wrote:
> Marc G. Fournier wrote:
> >
> >
> > > On Mon, 27 Oct 2003, Bruce Momjian wrote:
> > >
> > > > Marc G. Fournier wrote:
> > > > >
> > > > >
> > > > > On Mon, 27 Oct 2003, Bruce Momjian wrote:
> > > > >
> > > > > > Changes
> > > > > > ---
> > >
>
> I am putting together a DB that records information about a set of web
> sites and how they link to one another. As one site refers to another, I
> monitor the first site and then record when I find the referred site.
>
> [snip]
>
> I also have a function called add_site that adds the newly
On Mon, 27 Oct 2003 10:22:32 -0500, Tom Lane <[EMAIL PROTECTED]>
wrote:
>The low-tech solution to this would be to stop listing the default
>values as commented-out entries, but just make them ordinary uncommented
>entries.
Please not. How should we ask a newbie seeking assistance on one of
the s
56 matches
Mail list logo
