CREATE TYPE test (a int4, b int4);
COMMENT ON COLUMN test.a IS 'A column';
Seems harmless, but should we allow it?
Actually, currently it's bad because such comments will not be dumped by
pg_dump. Shall I fix pg_dump?
Chris
---(end of broadcast)---
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> On Mon, Jul 26, 2004 at 02:22:21AM +0200, Gaetano Mendola wrote:
>> In the release not I can read:
>> This allows columns to contain arbitrary composite types
>> like rows from other tables. [SNIPPED]
>>
>> Wasn't this alread true on 7.4 ?
> No, this i
Barry S <[EMAIL PROTECTED]> writes:
> > * The table contains one index: P1_NRN_ROAD_V (v, sobjid) (The index
> > includes the column sobjid because the query projects this col, and its
> > inclusion in the index allows it to be serviced without accessing the
> > underlying table)
(Unlike Oracle)
Gaetano Mendola <[EMAIL PROTECTED]> writes:
> kalman=# create table test ( a integer, b integer );
> CREATE TABLE
> kalman=# create table test1 ( c integer , d test );
> CREATE TABLE
> kalman=# alter table test drop column b;
> ALTER TABLE <--- Here I think the server shall complain abou
It's bizarre how you can comment on columns in composite types!
CREATE TYPE test (a int4, b int4);
COMMENT ON COLUMN test.a IS 'A column';
Seems harmless, but should we allow it?
Chris
---(end of broadcast)---
TIP 6: Have you searched our list archive
Gaetano Mendola <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
> | I was just looking around the net to see exactly what Oracle's PL/SQL
> | syntax is. It doesn't seem too unreasonable syntax-wise:
> | [ snip pl/sql syntax ]
> Is this sintax SQL standard driven ?
No, AFAIK it's just Oracle's sy
Simon Riggs <[EMAIL PROTECTED]> writes:
> CVS web interface has not been working for a few days. Not important
> right now, but something to fix soon-ish.
It works okay for me (modulo $PostgreSQL$ issue, see other thread).
What URL are you visiting to get the stated error?
On Sun, 2004-07-25 at 22:23, Tom Lane wrote:
> I don't think
> it's either practical or interesting to try to introduce an equivalent
> layering into Postgres.
I can possibly see a use for a row locking storage system, i.e. non MVCC
for some applications. But I can't see it being worth the amount
On Mon, 26 Jul 2004, Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Postgres was, however, one of the systems that in fact pioneered
> > pluggable storage managers. So we could say we're already one
> > generation ahead of everyone else: we had switchable storage managers,
> >
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Postgres was, however, one of the systems that in fact pioneered
> pluggable storage managers. So we could say we're already one
> generation ahead of everyone else: we had switchable storage managers,
> realized we didn't need them, and got rid of
Yeah, but the point was that he was doing an ALTER OWNER and needed to
fix the ACL to match. I thought he claimed to have written the needed
subroutine. I have not yet looked at his patch though.
I think Fabien's owner changing routine will end up being a strict
subset of my routine. I think hi
I reckon they could have a crack at implementing SQL2003 recursive
queries (eg. WITH syntax).
Or, SQL2003 ROLLUP and CUBE queries.
But that's just what I want :)
Chris
Bruce Momjian wrote:
I am forwarding this to hackers on behalf of some people who want to
improve PostgreSQL in India.
I suggest
Simon Riggs wrote:
> > For me, clarity and
> > candor gain a lot more credibility than trying to cover over missing
> > functionality in the past. I am not saying we have to be so honest that
> > we bash PostgreSQL, but in cases where we adjust wording to try to
> > prevent ourselves from looking
Marc G. Fournier wrote:
> On Sun, 25 Jul 2004, Bruce Momjian wrote:
>
> > Also, we need manual testing because people will do goofy things that
> > the test will not try, I am sure. :-)
>
> Agreed, but just want to make sure that Simon realizes that this 'level'
> of documentation is required
On Mon, 2004-07-26 at 00:55, Bruce Momjian wrote:
> Simon Riggs wrote:
> > On Sun, 2004-07-25 at 05:25, Bruce Momjian wrote:
> > > I have completed the 7.5 release notes. You can view them in HTML on
> > > the developer web page. I have marked a few items with question marks
> > > that need to be
On Mon, 2004-07-26 at 02:12, Marc G. Fournier wrote:
> On Sun, 25 Jul 2004, Bruce Momjian wrote:
>
> > Also, we need manual testing because people will do goofy things that
> > the test will not try, I am sure. :-)
>
> Agreed, but just want to make sure that Simon realizes that this 'level'
>
On Sun, 25 Jul 2004, Bruce Momjian wrote:
> I am forwarding this to hackers on behalf of some people who want to
> improve PostgreSQL in India.
>
> I suggest you read the developers FAQ on the developers page:
>
> http://developers.postgresql.org
>
> then subscribe to hackers to discuss feat
On Mon, Jul 26, 2004 at 02:22:21AM +0200, Gaetano Mendola wrote:
> In the release not I can read:
>
> #Allow arbitrary row expressions (Tom)
>
> This allows columns to contain arbitrary composite types
> like rows from other tables. [SNIPPED]
>
> Wasn't this alread true on 7.4 ?
No, this is a n
On Sun, 25 Jul 2004, Bruce Momjian wrote:
Also, we need manual testing because people will do goofy things that
the test will not try, I am sure. :-)
Agreed, but just want to make sure that Simon realizes that this 'level'
of documentation is required for release, not for beta ... in fact, be
n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'm playing with complex row type:
kalman=# create table test ( a integer, b integer );
CREATE TABLE
kalman=# create table test1 ( c integer , d test );
CREATE TABLE
kalman=# insert into test1 values ( 1, (2,3) );
INSERT 17277 1
kalman=# select
In the release not I can read:
#Allow arbitrary row expressions (Tom)
This allows columns to contain arbitrary composite types
like rows from other tables. [SNIPPED]
Wasn't this alread true on 7.4 ?
See:
kalman=# select version();
version
--
All fixed. Thanks.
---
Bruno Wolff III wrote:
> On Sun, Jul 25, 2004 at 00:25:43 -0400,
> Bruce Momjian <[EMAIL PROTECTED]> wrote:
> > I have completed the 7.5 release notes. You can view them in HTML on
> > the develope
Marc G. Fournier wrote:
> On Sun, 25 Jul 2004, Bruce Momjian wrote:
>
> > Marc G. Fournier wrote:
> >> On Sun, 25 Jul 2004, Simon Riggs wrote:
> >>
> >>> HIGH
> >>> 1. Documentation (sr) (now)
> >>> - Backup and Recovery chapter
> >>> - WAL chapter
> >>
> >> Docs, as always, can be delivered/impro
On Sun, 25 Jul 2004, Bruce Momjian wrote:
Marc G. Fournier wrote:
On Sun, 25 Jul 2004, Simon Riggs wrote:
HIGH
1. Documentation (sr) (now)
- Backup and Recovery chapter
- WAL chapter
Docs, as always, can be delivered/improved throughout beta ...
Yes, but without PITR docs there is no way to test th
\Tom Lane wrote:
> Bruno Wolff III <[EMAIL PROTECTED]> writes:
> > In the following paragraph there appear to be two typos. I think
> > "optimizer make" should be "optimizer makes" and that "lose-source"
> > should be "closed-source".
>
> > It is difficult to explain all the optimizer improvement
Bruno Wolff III wrote:
> On Sun, Jul 25, 2004 at 00:25:43 -0400,
> Bruce Momjian <[EMAIL PROTECTED]> wrote:
> > I have completed the 7.5 release notes. You can view them in HTML on
> > the developer web page. I have marked a few items with question marks
> > that need to be addressed. I am loo
Adjustment made:
http://pgfoundry.org/projects/pginstaller. This release
supports NT-based Windows releases like NT4, Win2k, XP, Win2003.
Older releases like Windows 95, 98, and ME are not supported because
these operating systems do not have the infrastructure to
All added. Thanks.
---
Andrew Dunstan wrote:
> Bruce Momjian said:
> > I have completed the 7.5 release notes. You can view them in HTML on
> > the developer web page. I have marked a few items with question marks
> > that
Simon Riggs <[EMAIL PROTECTED]> writes:
> Solution Design:
> Before a backup is taken, write a file to data directory that identifies
> which backup this is. When the backup is taken this file will be copied
> with the backup, and later restored when the backup is restored.
> When backup completes
Simon Riggs wrote:
> On Sun, 2004-07-25 at 05:25, Bruce Momjian wrote:
> > I have completed the 7.5 release notes. You can view them in HTML on
> > the developer web page. I have marked a few items with question marks
> > that need to be addressed. I am looking for improvements, even minor
> > o
Gaetano Mendola wrote:
> We have only one engine: the full transactional one. If the OP need
> to have for example the MEMORY one the he can easily create a RAM
> disk and with the tablespaces support he can create tables or index
> or whatever objects in memory.
Well, it certainly could make sens
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Lane wrote:
| Bruce Momjian <[EMAIL PROTECTED]> writes:
|
|>So it allows functions to use subtransactions and recover from errors.
|>I thought that was more than we could do for 7.5 and in fact the release
|>notes now saw that will be done in a futu
Gaetano Mendola wrote:
[ PGP not available, raw data follows ]
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Sun, 2004-07-25 at 05:25, Bruce Momjian wrote:
>
> |I have completed the 7.5 release notes. You can view them in HTML on
> |the developer web page. I have marked a few items w
I am forwarding this to hackers on behalf of some people who want to
improve PostgreSQL in India.
I suggest you read the developers FAQ on the developers page:
http://developers.postgresql.org
then subscribe to hackers to discuss feature additions. Thanks.
-
Marc G. Fournier wrote:
> On Sun, 25 Jul 2004, Simon Riggs wrote:
>
> > HIGH
> > 1. Documentation (sr) (now)
> > - Backup and Recovery chapter
> > - WAL chapter
>
> Docs, as always, can be delivered/improved throughout beta ...
Yes, but without PITR docs there is no way to test the feature.
Many
Andreas Pflug wrote:
Pierre Emmanuel Gros wrote:
In mysql, we can wrote a create table like CREATE TABLE t (i INT)
ENGINE = INNODB||BDB|;
where the storage engine is the innodb one.
MySQL needs this because they have a weird understanding of RDBMS.
This could be true, but the answer doesn't make
CVS web interface has not been working for a few days. Not important
right now, but something to fix soon-ish.
Best Regards, Simon Riggs
=
Error
Error: Unexpected output from cvs co: cvs [checkout aborted]: Absolute
module reference invalid: `/pgsql-serve
Problem Summary (from previous posts)
The archive recovery must stop AFTER the end of the backup which the
recovery used as its "starting point". If not, incorrect database states
are likely.
In general, this is a small window for error and procedures should exist
to return to the prior backup. No
Pierre Emmanuel Gros wrote:
> In mysql, we can wrote a create table like CREATE TABLE t (i
> INT) ENGINE = INNODB||BDB|; where the storage engine is the
> innodb one. This allow to have differents kind of storage
> format, and allow to easly implements memory table or remote
> table. I try to mak
Pierre Emmanuel Gros wrote:
In mysql, we can wrote a create table like CREATE TABLE t (i INT) ENGINE
= INNODB||BDB|;
where the storage engine is the innodb one.
MySQL needs this because they have a weird understanding of RDBMS.
There's absolutely no sense in trying to transfer this stuff into
Po
murphy pope <[EMAIL PROTECTED]> writes:
> I don't get it. Why would database access fail during an aborted
> transaction?
Because we've already aborted the transaction (released its locks,
for instance). In a real sense you don't have a transaction at all
anymore.
> Can anyone explain? I've do
Simon Riggs <[EMAIL PROTECTED]> writes:
> On Tue, 2004-07-20 at 15:00, Tom Lane wrote:
>> Yeah, but the WASTED_SPACE/FILE_HEADER stuff is already pretty ugly, and
>> adding two more warts to the code to support it is sticking in my craw.
>> I'm thinking it would be cleaner to treat the extra labeli
> * The table contains one index: P1_NRN_ROAD_V (v, sobjid) (The index
> includes the column sobjid because the query projects this col, and its
> inclusion in the index allows it to be serviced without accessing the
> underlying table)
> Now, for the queries:
>
> QUERY 2: select sobjid from p1_nr
I just had a thought; was looking at a script where I'd rather invoke
using psql than using a Perl module (since Pg/DBD that might very well
not be available on AIX, HP/UX, Solaris, or such).
What would be very nice would be for there to be a psql command option
that would accept a "DSN" as oppose
Hi everyone...my name is Mike MacEachern. I work with a technical search
firm in Toronto - ARES Consulting
A client of mine in Toronto is utilizing Linux technology to drive their
business forward. The company is keen to hire two solid Postgres
DBA's --they're very hard to find! These are in produ
At the top of backend/parser/gram.y there's a big comment that says "don't do any database access during the parse phase, just in case we're in the middle of an aborted transaction".
I don't get it. Why would database access fail during an aborted transaction? Any changes have to be thrown a
In mysql, we can wrote a create table like
CREATE TABLE t (i INT) ENGINE = INNODB||BDB|;
where the storage engine is the innodb one.
This allow to have differents kind of storage format, and allow to easly implements memory table or remote table.
I try to make the same thing for postgresql but i
Mark Kirkwood <[EMAIL PROTECTED]> writes:
> Looks good to me. Log file numbering scheme seems to have changed - is
> that part of the fix too?.
That's for timelines ... it's not directly related but I thought I
should put in both changes at once to avoid forcing an extra initdb.
Looks good to me. Log file numbering scheme seems to have changed - is
that part of the fix too?.
Tom Lane wrote:
This is done in CVS tip. Mark, could you retest to verify it's fixed?
regards, tom lane
---(end of broadcast)---
TIP 1: subscrib
>Btw, can 7.5 run on WinCE
No.
>/XP Media Center/
Probably, but AFAIK not tested.
>XP SP2
Yes (haven't tested with the very latest versions of the SP, but it
works with the earlier ones)
>/etc?
Works fine on the PDC build of Longhorn...
//Magnus
---(end of broadcast)---
Bruce Momjian wrote:
I have completed the 7.5 release notes. You can view them in HTML on
the developer web page. I have marked a few items with question marks
that need to be addressed. I am looking for improvements, even minor
ones. Either send in a patch or committers can modify the file
dir
Bruno Wolff III <[EMAIL PROTECTED]> writes:
> In the following paragraph there appear to be two typos. I think
> "optimizer make" should be "optimizer makes" and that "lose-source"
> should be "closed-source".
> It is difficult to explain all the optimizer improvements that go into a release
> l
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Is it just me or the resowner.c file does not have $PostgreSQL$
> expanded?
I see
*$PostgreSQL: pgsql-server/src/backend/utils/resowner/resowner.c,v 1.1
2004/07/17 03:30:10 tgl Exp $
> May it be related to the fact that I'm using CVSup?
Pro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 2004-07-25 at 05:25, Bruce Momjian wrote:
|I have completed the 7.5 release notes. You can view them in HTML on
|the developer web page. I have marked a few items with question marks
|that need to be addressed. I am looking for improvements,
On Sun, 25 Jul 2004, Simon Riggs wrote:
HIGH
1. Documentation (sr) (now)
- Backup and Recovery chapter
- WAL chapter
Docs, as always, can be delivered/improved throughout beta ...
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED] Yah
On Sun, Jul 25, 2004 at 00:25:43 -0400,
Bruce Momjian <[EMAIL PROTECTED]> wrote:
> I have completed the 7.5 release notes. You can view them in HTML on
> the developer web page. I have marked a few items with question marks
> that need to be addressed. I am looking for improvements, even minor
I had datadir in /dir1 and I started postmaster with:
postmaster -D /dir1
this recorded "-D /dir1" in /dir1/postmaster.opts. Then I stopped
postmaster and moved /dir1 to /dir2. I then started postmaster with:
PG_DATA=/dir2 pg_ctl start
It worked normally. But:
PG_DATA=/dir2 pg_ctl restart
fail
When postmaster fails to run due to e.g. datadir being set to 755,
'pg_ctl start' incorrectly reports "postmaster successfully started".
I'm not sure how to fix this though. Do a [shorter] wait for 'start'
mode by default? Install a child handler (can you even do that with
shell script?)
This
Bruce Momjian said:
> I have completed the 7.5 release notes. You can view them in HTML on
> the developer web page. I have marked a few items with question marks
> that need to be addressed. I am looking for improvements, even minor
> ones. Either send in a patch or committers can modify the f
On Sun, 2004-07-25 at 05:25, Bruce Momjian wrote:
> I have completed the 7.5 release notes. You can view them in HTML on
> the developer web page. I have marked a few items with question marks
> that need to be addressed. I am looking for improvements, even minor
> ones. Either send in a patch
On Sun, 2004-07-25 at 04:22, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Other than the spectacular lack of documentation, I don't think we are
> >> in bad shape at all.
>
> > OK, that helps. Alvaro had a number of items floating around and I
> > wasn't sur
Is it just me or the resowner.c file does not have $PostgreSQL$
expanded?
May it be related to the fact that I'm using CVSup? However I have the
line
tag=PostgreSQL=CVSHeader
in CVSROOT/options ...
Also I see that in all files, the $PostgreSQL$ tag shows a version
number that's one less than the
62 matches
Mail list logo
