"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> Right now, from what I can tell, the snapshot looks great to me:
That looks up-to-date to me too, but where did you get it from?
The copy I pulled just now from
ftp://ftp.us.postgresql.org/dev/postgresql-snapshot.tar.gz
has still got the problem:
On Sat, 13 Oct 2001, Bill Studenmund wrote:
> On Sat, 13 Oct 2001, Tom Lane wrote:
>
> > I also wonder how the fixed, single-level namespace search path you
> > describe interacts with the SQL rules for schema search. (I don't
> > actually know what those rules are offhand; haven't yet read the
On Sat, 13 Oct 2001, Tom Lane wrote:
> Bill Studenmund <[EMAIL PROTECTED]> writes:
> > The other choice is to just give the function's name. The first place
> > Postgres will look is in the package context used for parsing. If it's not
> > there (and that context wasn't "standard"), then it will
On Mon, 15 Oct 2001, Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > Right now, from what I can tell, the snapshot looks great to me:
>
> That looks up-to-date to me too, but where did you get it from?
> The copy I pulled just now from
> ftp://ftp.us.postgresql.org/dev/postgr
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> ... work for you with code built from the cvs tip? I did an update and
> build tonight and see
> myst$ postmaster -i
> postgres: invalid option -- r
Hmm. I was fooling with postmaster.c & postgres.c last night.
I didn't think I touched parameter par
Sorry about that message. My mailer had a bad reply format.
--
ICQ: 15605359 Bicho
=^..^=
First, they ignore you. Then they laugh at you. Then they fight you. Then you win.
Mahatma Gandhi.
Por que no pensaran los hombres como los animales? Pink Panther.
-- Forwarded message --
Date: Fri, 19 Oct 2001 08:22:46 -0600
From: David Eduardo Gomez Noguera <[EMAIL PROTECTED]>
To: "Ron de Jong" <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: [HACKERS] Is there no "DESCRIBE ;" on PGSQL? help!!!
on psql, do \? there are a lot o
Gunnar =?iso-8859-1?q?R=F8nning?= <[EMAIL PROTECTED]> writes:
> Hmm. But if we had schema support can't we just package those procedures
> into a schema with a given name ? Maybe my stored procedures needs some other
> resources as well that should not conflict with other packages, like temp
> tab
> We do "optind = 1"
> in SSDataBase, but maybe on your platform, we need to do more than that
> to point getopt at the correct arglist. Any ideas?
Ah ... I betcha your platform needs optreset = 1. Fix coming ...
regards, tom lane
---(end of bro
> Ah ... I betcha your platform needs optreset = 1. Fix coming ...
I've just committed this. Please update and let me know if it helps.
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once w
On Fri, 19 Oct 2001, Ron de Jong wrote:
> Any idea to get a human readable list with column descriptions like
> type,size,key,default,null.
> It would be nice if it would look simular to the mysql variant:
>
> mysql> describe employee;
> +---+--+--+-+-+
Michael Meskes wrote:
> On Tue, Oct 16, 2001 at 10:27:42AM +0100, Lee Kindness wrote:
> > And the patch below corrects a pet peeve I have with ecpg, all errors
> > and warnings are output with a line number one less than reality...
>
> I wish I knew where this comes from. I've been trying to trac
On Thu, 18 Oct 2001, Peter Eisentraut wrote:
> Bill Studenmund writes:
>
> > Honestly, I do not understand why "global variables" have been such a sore
> > point for you.
>
> My point is that the proposed "package support" introduces two features
> that are a) independent, and b) already exist, a
>
> Right now, from what I can tell, the snapshot looks great to me:
>
> postgresql# ls -lt
> total 486
> drwxrwxrwx 15 pgsql pgsql 512 Oct 15 04:04 src
> drwxrwxrwx 43 pgsql pgsql1024 Oct 15 04:04 contrib
> drwxrwxrwx 4 pgsql pgsql 512 Oct 15 04:04 doc
> drwxrwxrwx 2 pgsql
Peter Eisentraut writes:
> Lee Kindness writes:
> > For your information I've attached the man page for the Sun C
> > compiler, which explicitly lists the -h and -R flags.
> I didn't read much farther than
> acc (SPARC only) is not intended to be used directly on
> Solaris 2.
On Sat, 13 Oct 2001, Peter Eisentraut wrote:
> Bill Studenmund writes:
>
> > So what are packages? In Oracle, they are a feature which helps developers
> > make stored procedures and functions.
>
> I think you have restricted yourself too much to functions and procedures.
> A package could/should
> Matthew Hagerty <[EMAIL PROTECTED]> writes:
> > but I also want to check the connection *before* submitting a
query...
If you mean directly before the query, then forget it, as Tom already
said :-)
> This strikes me as utterly pointless. You'll need to be able to
recover
> from query failure
Any idea to get a human readable list with column
descriptions liketype,size,key,default,null.It would be nice if it would
look simular to the mysql variant:mysql>
describe
employee;+---+--+--+-+-++|
Field | Type | Null | Key |
Defaul
Thus spake Tom Lane
> [EMAIL PROTECTED] (D'Arcy J.M. Cain) writes:
> > I have tons of old files with names like base/db/pg_sorttemp.##. I
> > assume that they are temporary sorting files but somehow they never got
> > cleared out. Is it safe to delete these from a running system. The files
* Bill Studenmund <[EMAIL PROTECTED]> wrote:
|
| Packages aren't schemas. What they bring to the table is they facilitate
| making stored procedures (functions). You can have twelve different
| developers working on twenty different packages, with no fear of name
| conflicts. The package names wil
[EMAIL PROTECTED] (D'Arcy J.M. Cain) writes:
>> BTW, if you are seeing unreclaimed sorttemp files in a recent release
>> (7.0 or later), I'd like to know about it. That shouldn't happen,
>> short of a backend crash anyway...
> Well, I had over 6,000 of these files. This database is about a year
...
> All three of these cases work just fine for me. Maybe some platform
> dependency has snuck in? Hard to see how though. It looks like the
> failure is occurring when the postmaster launches the xlog startup
> subprocess. The building of the argument list for that subprocess is
> fixed and
On 19 Oct 2001, Gunnar [iso-8859-1] Rønning wrote:
> * Bill Studenmund <[EMAIL PROTECTED]> wrote:
> |
> | Packages aren't schemas. What they bring to the table is they facilitate
> | making stored procedures (functions). You can have twelve different
> | developers working on twenty different pac
On 19 Oct 2001, Gunnar [iso-8859-1] Rønning wrote:
> * Tom Lane <[EMAIL PROTECTED]> wrote:
> |
> | Yeah. I am wondering whether we couldn't support Oracle-style packages
> | as a thin layer of syntactic sugar on top of schemas. I am concerned
> | about the prospect that "foo.bar" might mean eit
On Fri, 19 Oct 2001, Tom Lane wrote:
> Yeah. I am wondering whether we couldn't support Oracle-style packages
> as a thin layer of syntactic sugar on top of schemas. I am concerned
> about the prospect that "foo.bar" might mean either "object bar in
> schema foo" or "object bar in package foo".
Hi,
Version 7.1.3, Linux 2.2.18
Following procedure:
1. pg_dump dbname > outfile
Everything is fine.
2. Recreating the database on another system (same Versions)
psql dbname < infile
I get once:
ERROR: parser: parse error at or near ","
The rest works fine.
Debug -d2 shows that recreating a
On Tue, 16 Oct 2001, Bill Studenmund wrote:
> I still think that schemas and packages are different, but I now think
> they are interrelated. And that it shouldn't be too hard to leverage the
> package work into schema support. Still a lot of work, but the package
> work has shown how to go from
"Johann Zuschlag" <[EMAIL PROTECTED]> writes:
> DEBUG: query: CREATE OPERATOR <> (PROCEDURE = numeric_neq ,
> LEFTARG = numeric ,
> RIGHTARG = double precision ,
> COMMUTATOR = <> ,
> NEGATOR = ,
> RESTRICT = eqsel ,
> JOIN = eqjoinsel );
> ERROR:
On Fri, Oct 19, 2001 at 09:37:59AM +0200, Christof Petig wrote:
> I somewhat got the impression that using C++ style comments (//) are related
> to worse the problem. But I must confess I didn't dig deep enough to contribute
> anything substancial. Perhaps the problem is a misunderstanding of ecp
Marc,
I've noticed (and not only me) significant slowdown of search at
fts.postgresql.org.
>From our logs:
...
Sun Aug 19 03:32:00 EDT 2001
/usr/local/mailware/CORE/bin/vacuum_analyze: /usr/local/pgsql/bin/psql: No such
file or directory
...
Sun Oct 14 03:32:00 EDT 2001
/usr/local/mailware/CORE
psql \d command.
> Any idea to get a human readable list with column descriptions like
> type,size,key,default,null.
> It would be nice if it would look simular to the mysql variant:
>
> mysql> describe employee;
> +---+--+--+-+-++
> | Field
Patch applied. Thanks. Patch attached. autoconf run.
---
> Hi!
>
> Without this patch I couldn't compile PostgreSQL on Solaris 8 x86 using
> Sun's compiler. May be it will be usefull for someone else?
>
> Regards
> De
* Tom Lane <[EMAIL PROTECTED]> wrote:
|
| > resources as well that should not conflict with other packages, like temp
| > tables or such. It then seems to me that using schemas can solve everything
| > that packages do and more ?
|
| Yeah. I am wondering whether we couldn't support Oracle-style
Yes, we inherited these arrays from Berkeley and haven't had any need to
remove them. Are you trying to do things that the other interfaces like
ODBC and JDBC don't handle?
The group array is a hack but the pg_proc array would be hard to replace
becauseit acts as part of the unique key used for
I have traced down the postmaster-option-processing failure that Thomas
reported this morning. It appears to be specific to systems running
glibc: the problem is that resetting optind to 1 is not enough to
put glibc's getopt() subroutine into a good state to process a fresh
set of options. (Inte
Using current sources, the following sequence:
set DateStyle TO 'Postgres';
set TimeZone TO 'PST8PDT';
select '2001-09-22T18:19:20'::timestamp(2);
produces
timestamptz
--
Sat Sep 22 11:19:20 2001 PDT
on my HPUX box, and evidently also on your machine becau
> Using current sources, the following sequence:
> set DateStyle TO 'Postgres';
> set TimeZone TO 'PST8PDT';
> select '2001-09-22T18:19:20'::timestamp(2);
> produces... (snip) ...
> on my HPUX box, and evidently also on your machine because that's
> what's in the timestamptz expected file. Howeve
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> (I still see the symptom btw; did a make distclean and configure after
> updating my tree)
Yeah, it's still busted; my first try was wrong. I have confirmed the
"optind = 0" fix works on my LinuxPPC machine, but we need to decide
how to autoconfigure
I've applied patches; all regression tests pass and the
'yyy-mm-ddThh:mm:ss' is now handled correctly afaict.
There is an ongoing issue regarding precision and rounding for cases
with large interval spans. I've patched the tree with a possible
solution involving counting significant figures befor
(I still see the symptom btw; did a make distclean and configure after
updating my tree)
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Hello all!!
I'm developer of a interface for PostgreSQL for the Borland Kylix
and Delphi tools (http://www.vitavoom.com). I've run into the following
problems with catalogs:
- pg_group: the grolist field is an array. How can I make a query
that tell me the usernames of a group ?
> ... work for you with code built from the cvs tip? I did an update and
> build tonight and see
A bit more information: an unadorned "-i" fails:
myst$ postmaster -i
postgres: invalid option -- r
Usage:
postgres -boot [-d] [-D datadir] [-F] [-o file] [-x num] dbname
-d debug mo
use /usr/local/bin/psql
Vince.
On Fri, 19 Oct 2001, Oleg Bartunov wrote:
> Marc,
>
> I've noticed (and not only me) significant slowdown of search at
> fts.postgresql.org.
>
> >From our logs:
>
> ...
> Sun Aug 19 03:32:00 EDT 2001
> /usr/local/mailware/CORE/bin/vacuum_analyze: /usr/local/pg
Thanks for that.
I'll have to work around this by extracting all character variable data and
'hard coding' this into the SQL statement before I SQLExecute() the
statement. I had to do the same for ... Oracle (sorry for swearing).
Do you (or anyone else for that matter) know if/when UNICODE bindi
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> ... work for you with code built from the cvs tip? I did an update and
> build tonight and see
> myst$ postmaster -i
> postgres: invalid option -- r
I just rebuilt from cvs tip, and I don't see any such problem...
anyone else?
hasn't been in /usr/local/pgsql/bin since Aug 18th ...
hub# ls -lt `which psql`
-rwxr-xr-x 1 root wheel 108472 Aug 16 08:55 /usr/local/bin/psql
On Fri, 19 Oct 2001, Oleg Bartunov wrote:
> Marc,
>
> I've noticed (and not only me) significant slowdown of search at
> fts.postgresql.org.
>
> Fr
On Fri, 19 Oct 2001, Vince Vielhaber wrote:
>
> use /usr/local/bin/psql
ok.
>
>
> Vince.
>
> On Fri, 19 Oct 2001, Oleg Bartunov wrote:
>
> > Marc,
> >
> > I've noticed (and not only me) significant slowdown of search at
> > fts.postgresql.org.
> >
> > >From our logs:
> >
> > ...
> > Sun Aug 1
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> A bit more information: an unadorned "-i" fails:
> myst$ postmaster -i
> postgres: invalid option -- r
> But no arguments succeeds:
> myst$ postmaster
> And multiple arguments succeeds (without damaging the other arguments):
> myst$ postmaster -i -p 1
48 matches
Mail list logo
