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 "+
"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
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.
>
>
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
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
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
Dror Matalon <[EMAIL PROTECTED]> writes:
> On Tue, Oct 28, 2003 at 02:55:17PM -0500, Tom Lane wrote:
>> Dror Matalon <[EMAIL PROTECTED]> writes:
> Oct 28 01:04:50 ... postgres[7572]: [52227-1] PANIC: can't juggle and compress too
> What does the error message mean?
It's an unimplemented case in
through my patented unit testing technology (caffein and sleep deprivation)
I came across this:
db=> SELECT 1 FROM object WHERE object IS NOT NULL;
ERROR: unrecognized node type: 302
where I was expecting something more like this:
db=> SELECT 1 FROM object WHERE mispelt_column IS NOT NULL;
ERROR
On Tue, Oct 28, 2003 at 02:55:17PM -0500, Tom Lane wrote:
> Dror Matalon <[EMAIL PROTECTED]> writes:
> > Oct 28 01:04:50 ... postgres[7572]: [52227-1] PANIC: can't juggle and compress too
>
> Oh? I don't suppose you have a way to reproduce this :-(
No not really. It's been running for a few ho
Dror Matalon <[EMAIL PROTECTED]> writes:
> Oct 28 01:04:50 ... postgres[7572]: [52227-1] PANIC: can't juggle and compress too
Oh? I don't suppose you have a way to reproduce this :-(
regards, tom lane
---(end of broadcast)---
Freebsd 4.9
Postgres 7.4Beta5
We have a daemon that among other things vacuums the channels table
every 5 minutes. Worked fine until last night.
Oct 28 01:04:49 ... postgres[7572]: [52226-1] LOG: statement: VACUUM ANALYZE channels
Oct 28 01:04:50 ... postgres[7572]: [52227-1] PANIC: can't juggl
18 matches
Mail list logo
