I get the following when I build from CVS:
gcc -I../../../src/include -I../../../src/interfaces/libpq -O2 -g -Wall
-Wmissing-prototypes -Wmissing-declarations -o pg_dump pg_dump.o common.o
pg_backup_archiver.o pg_backup_db.o pg_backup_custom.o pg_backup_files.o
pg_backup_null.o pg_backup_tar.o
Philip Warner wrote:
> I get the following when I build from CVS:
>
> gcc -I../../../src/include -I../../../src/interfaces/libpq -O2 -g -Wall
> -Wmissing-prototypes -Wmissing-declarations -o pg_dump pg_dump.o common.o
> pg_backup_archiver.o pg_backup_db.o pg_backup_custom.o pg_backup_files.o
>
Nope, neigher PyGreSQL nor ""PGSQL"" are products of
Pgsql.com (aka PostgreSQL Inc)On Mon, 9 Oct 2000, Vince Vielhaber wrote:
> On Mon, 9 Oct 2000, Bruce Momjian wrote:
>
> > I need to know how this is different than our current python interface,
> > PyGreSQL.
>
> Is this a product of pgsql.com
The Hermit Hacker wrote:
>
> On Mon, 9 Oct 2000, Bruce Momjian wrote:
>
> Ya, but in one email, you appear to agree with me ... then Tom posts a
> good point and you jump over to that side ... at least pick a side? :) I
> too wish to see it implemented, I just don't want to have to double my
>
> > -Wmissing-prototypes -Wmissing-declarations -o pg_dump pg_dump.o common.o
> > pg_backup_archiver.o pg_backup_db.o pg_backup_custom.o pg_backup_files.o
> > pg_backup_null.o pg_backup_tar.o -L../../..
> > /src/interfaces/libpq -lpq -lz -lcrypt -lnsl -ldl -lm -lreadline -lncurses
> > -lz
> > ../
On Sun, Oct 08, 2000 at 01:37:45PM -0400, Bruce Momjian wrote:
> > But perhaps it is ecpg's fault for including "elog.h".
> > IMHO these defines should never leave the database kernel.
> ...
> Yes, leaking into user programs is a bad practice. Is there a
> solution/patch for that?
Hmm, I haven'
On Tue, 10 Oct 2000, Jeff MacDonald wrote:
> Nope, neigher PyGreSQL nor ""PGSQL"" are products of
> Pgsql.com (aka PostgreSQL Inc)On Mon, 9 Oct 2000, Vince Vielhaber wrote:
I knew PyGreSQL wasn't but PgSQL appeared a bit misleading. Thanks
for clearing that up. I guess on the website I should
The Hermit Hacker writes:
> > > > Announce: Release of PyGreSQL version 3.0
> >
> > When is 7.1 being locked down? I may be releasing 3.1 with a few small
> > fixes and changes very soon.
>
> you should be safe until mid-december or so ... as PyGreSQL doesn't affect
> the build of PostgreSQL i
Bruce Momjian writes:
> I need to know how this is different than our current python interface,
> PyGreSQL.
> > PgSQL is a package of two (2) modules that provide a Python DB-API 2.0
> > compliant interface to PostgreSQL databases.
DB-API is the standard database interface for Python. Kind of
Hiroshi Inoue writes:
> For example the following line
> CFLAGS+= -DFRONTEND -I$(srcdir)
> in makefiles doesn't work currently.
>
> I found the recent change in Makefile.global.in.
> ifeq ($(GCC), yes)
> override CFLAGS += -Wall -Wmissing-prototypes -Wmissing-declarations
> endif
Seems
Is the following expected behavior for a UNION query with ORDER BY:
executing this query:
+++
SELECT a.attnum as number,
a.attname as attribute,
CASE WHEN t.typname = 'varchar' THEN
t.typname || '(' || a.atttypmod - 4
Actually with version 3.0 of PyGreSQL there is a
DB-API v2.0 compliant wrapper pgdb.py.
--- Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Bruce Momjian writes:
>
> > I need to know how this is different than our
> current python interface,
> > PyGreSQL.
>
> > > PgSQL is a package of two (2) mod
Michael Fork <[EMAIL PROTECTED]> writes:
> However, if I execute the same query and drop "a.attnum as number" from
> the select part, it returns the following:
> ...
> which is incorrect accoring to the initial query. It appears to be
> ordering the individual selects and then appending the secon
"Billy G. Allie" <[EMAIL PROTECTED]> writes:
> Peter Eisentraut wrote:
>> Sounds interesting, but isn't "pgsql" an extremely unfortunate choice of
>> name, given that it's already used as an abbreviation for "PostgreSQL"?
> PgSQL is the name of the module you import in Python to access a PostgreS
Maybe I'm just overlooking something really simple but this has me a bit
confused.
What I'm trying to do is get the amount of time from A to B -- I thought
age() would do just that but it seems to be about a day off sometimes.
hhs=# SELECT age('Sun Dec 03 08:00:00 2000 EST','Tue Oct 10 08:00:00
> I should point out that it works as I expected it to on other values..
>
> hhs=# SELECT age('Sun Nov 05 08:00:00 2000 EST','Tue Oct 10 08:00:00 2000
> EDT') as esec;
>esec
> --
> @ 26 days 1 hour
> (1 row)
>
> hhs=# SELECT ('Tue Oct 10 08:00:00 2000 EDT'::timestamp + '1
Would it be politically incorrect to combine named templates (including
port makefiles, etc.) into one, since they all do the same thing anyway?
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
On Tue, Oct 10, 2000 at 11:40:17PM +0200, Peter Eisentraut wrote:
> Would it be politically incorrect to combine named templates (including
> port makefiles, etc.) into one, since they all do the same thing anyway?
i'm not sure about openbsd, but freebsd likes to install "packages" into
/usr/loca
I don't see this in the tree. Status, please.
>
> Attached is a first attempt at implementing the classoid feature. It
> works! Can the postgres gurus comment if I've done it right and point
> out any problems. A lot of it was guess work so I'm sure it can be
> cleaned up some.
>
> --
> Chris
On Tue, 10 Oct 2000, Peter Eisentraut wrote:
> Would it be politically incorrect to combine named templates (including
> port makefiles, etc.) into one, since they all do the same thing anyway?
Don't forget bsdi. Lately they've all been referring to the group of
them as bsd.
Vince.
--
=
It's TableOid now. That patch is long dead...
regards, tom lane
On Tue, 10 Oct 2000, Billy G. Allie wrote:
> Tom Lane wrote:
> > "Billy G. Allie" <[EMAIL PROTECTED]> writes:
> > > Peter Eisentraut wrote:
> > >> Sounds interesting, but isn't "pgsql" an extremely unfortunate choice of
> > >> name, given that it's already used as an abbreviation for "PostgreSQL"
Peter Eisentraut wrote:
> Hiroshi Inoue writes:
>
> > For example the following line
> > CFLAGS+= -DFRONTEND -I$(srcdir)
> > in makefiles doesn't work currently.
> >
> > I found the recent change in Makefile.global.in.
> > ifeq ($(GCC), yes)
> > override CFLAGS += -Wall -Wmissing-protot
Bruce Momjian <[EMAIL PROTECTED]> writes:
> more in voliation of the original plan.
>
violation ? Or is this just another gap in my knowledge of the English
language ?
Gunnar
As promised, the press release is at:
http://www.greatbridge.com/news/p_101020001.html
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be
Can I ask on a status?
> At 10:17 26/06/00 +0200, Zeugswetter Andreas SB wrote:
> >
> >A problem I see with an index at file end is, that you will need to read the
> >file twice, and that may be very undesireable if e.g the backup is on tape
> >or a compressed file.
>
> The proposal has actually
I think our source tree has diverged quite a bit from 7.0.2. Could you
grab a snapshot and let me know what needs changing for Solaris?
Thanks.
> I'm in the process of fixing build problems in 7.0.2 for Solaris CC
> (not GCC).
>
> 1. I'm curious why src/template/solaris_sparc_cc contains:
> -
I can confirm this is still a bug.
>
> A minor nasty error I got when trying to improve the query used to disable
> triggers:
>
> create table t1(f1 int4, f2 int4);
> create table t2(f1 int4, f2 int4);
>
> insert into t1 values(1, 0);
> insert into t1 values(2, 0);
>
> insert into t2 values(
Bruce Momjian wrote:
>
> As promised, the press release is at:
>
> http://www.greatbridge.com/news/p_101020001.html
Wow. Nice. The combined qualifications of the six steering committee
members are staggering.
Me, I'm just a lowly broadcast engineer with ten years experience and a
mea
Philip, where did we leave this?
>
> If anyone is interested in being sent the current sources for the new
> pg_dump & pg_restore, please let me know.
>
> The utilities now seem to work, but need testing.
>
> The basic idea is to use pg_dump to dump an *entire* database, and then use
> pg_rest
At 20:49 10/10/00 -0400, Bruce Momjian wrote:
>Can I ask on a status?
Done.
Philip Warner| __---_
Albatross Consulting Pty. Ltd. |/ - \
(A.B.N. 75 008 659 498) | /(@) __
This relates to large objects too.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup.| Drexel Hill, Pennsylvania 19026
At
If anyone was following my request to have a large object api for TOAST,
this is of interest.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be yo
At 21:01 10/10/00 -0400, Bruce Momjian wrote:
>Philip, where did we leave this?
In CVS. ;-).
The longer answer is that it's been in CVS for a while, and I have a
version for 7.0.2 which I have also been using for a while. Various people
have tested it, but not as many or as much as I would like
On Wed, 11 Oct 2000, Christopher Sawtell wrote:
> On Wed, 11 Oct 2000, [EMAIL PROTECTED] wrote:
> > > The project name on SourceForge is "Python Interface to PostgreSQL".
> >
> > How about PIPgSQL or piPgSQL?
>
> Perhaps Pi2PgSQL, or PySQL_ba
PySQL_ba? *grin*
I am tempted to apply this. This is the second person who asked for
binding to a single port. The patch looks quite complete, with doc
changes. It appears to be a thorough job.
Any objections?
> Your name : David MacKenzie
> Your email address: [EMAIL PROTECTED]
>
On Tue, 10 Oct 2000, The Hermit Hacker wrote:
> On Wed, 11 Oct 2000, Christopher Sawtell wrote:
>
> > On Wed, 11 Oct 2000, [EMAIL PROTECTED] wrote:
> > > > The project name on SourceForge is "Python Interface to PostgreSQL".
> > >
> > > How about PIPgSQL or piPgSQL?
> >
> > Perhaps Pi2PgSQL, o
Bruce Momjian wrote:
>
> I am tempted to apply this. This is the second person who asked for
> binding to a single port. The patch looks quite complete, with doc
> changes. It appears to be a thorough job.
A cursory inspection makes it look like the socket file can be placed
_anywhere_ -- eve
Peter Eisentraut wrote:
> Billy G. Allie writes:
>
> > PgSQL v1.0 has been released. This is the first public release of PgSQL.
> > It is available at http://sourceforge.net/projects/pgsql.
>
> Sounds interesting, but isn't "pgsql" an extremely unfortunate choice of
> name, given that it's alre
> > create table t1
> > (
> > f1 integer,
> > f2 integer
> > );
> >
> > create table t2
> > (
> > f1 integer references t1(f1),
> > f2 integer
> > );
>
> > begin transaction;
> > insert into t1(f1,f2) values(1,1);
> > delete from t1 where f1=1;
>
> > ERROR: trig
On Tue, 10 Oct 2000, Bruce Momjian wrote:
> I am tempted to apply this. This is the second person who asked for
> binding to a single port. The patch looks quite complete, with doc
> changes. It appears to be a thorough job.
>
> Any objections?
>From a quick read of his "description of probl
Tom Lane wrote:
> "Billy G. Allie" <[EMAIL PROTECTED]> writes:
> > Peter Eisentraut wrote:
> >> Sounds interesting, but isn't "pgsql" an extremely unfortunate choice of
> >> name, given that it's already used as an abbreviation for "PostgreSQL"?
>
> > PgSQL is the name of the module you import in
At 01:02 PM 10/10/00 -0400, Tom Lane wrote:
>Bottom line is we're not sure what to do now. Opinions from the
>floor, anyone?
Yeah, quit worrying and work your collective butts off on 7.1 and 7.2 :)
Seriously...the core group is obviously committed to PG, and appear to
be folks of integrity.
* Bruce Momjian <[EMAIL PROTECTED]> [001010 18:36] wrote:
> I am tempted to apply this. This is the second person who asked for
> binding to a single port. The patch looks quite complete, with doc
> changes. It appears to be a thorough job.
>
> Any objections?
I know several other people were
At times I need to call PQendcopy, how to I determine that it won't
block me waiting for output from the backend?
--
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
"I have the heart of a child; I keep it in a jar on my desk."
Christopher Sawtell wrote:
> On Wed, 11 Oct 2000, [EMAIL PROTECTED] wrote:
> > > The project name on SourceForge is "Python Interface to PostgreSQL".
> > How about PIPgSQL or piPgSQL?
> Perhaps Pi2PgSQL, or PySQL_ba
PyGSQyl.
Anagram fun on "PostgreSQL":
PostgreSQL=
Eg: Ports SQL
Gets Pro SQL
G
Hello,
I have quite strange behavior of the following SQL:
insert into address (cid,email) select distinct '49'::int,member.email from
member imit 1 ;
It should insert just 1 record.
But it insert all recodrs which will be selected by subselect...
What's wrong with this SQL? Or this is a bug?
47 matches
Mail list logo
