)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
to be
'infinity'. NULL implies they will expire, we're just not sure when.
Infinity shows that we do not intend to expire the user -- which is more
in-line with the actual implementation.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally
in time, feel free to ask for a hand.t
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
text - join array elements into a
string using given string delimiter
I'm open to opinions on implode() -- I only picked implode() because
that's what it is called in PHP. Any suggestions?
I think implode() and explode() go together. split() and join() are a
pair. Pick one ;)
--
Rod
for PostgreSQL to have this as a configuration
setting?
I think we already support this. Create a new character set with upper
/ lower case specified as being equal and PostgreSQL should behave as
expected.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
for a case sensitive comparison. Problem is, they don't (didn't)
support functional indexes -- so you simply couldn't make one.
End up with: WHERE field = 'var' and strcasecmp(field, 'var') everywhere
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description
this definitively.
Rod Taylor wrote:
On Wed, 2003-03-12 at 12:57, [EMAIL PROTECTED] wrote:
--le 12/03/2003 09:03 -0500, mlw écrivait :
| I was at a client office reviewing some code. They use MSSQL and I |
noticed that:
|
| select * from table where field = 'blah';
| gave the same results
to do
with 2 phase commits -- but were used as a marker to direct replication.
We may want to consider leaving some space for a server / server style
communication (Cluster ID, etc.)
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description
.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
On Mon, 2003-03-10 at 14:30, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
I'd be tempted to make a startup packet that will allow libpq to revert
back to old protocols easily enough for the future so that we can do=20
incremental changes to the protocol.
We already have that: you
On Mon, 2003-03-10 at 14:52, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
We already have that: you send a startup packet with a version less than
the latest, and the backend speaks that version to you.
Yes, but that requires you know the backend is less than the latest
that.
Enforcing spec seems like the least confusing mode to operate under,
especially given it could break simply by changing the plan -- which
happens automagically (seemingly random).
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally
be?
No. Can anyone offer data on when this started?
I see passes on March 2nd, updated and see passes today.
Did 5 runs of make check on today source.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
time...
It could be an order dependency in a parallel group.
The sequential runs don't throw a periodic error do they?
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
/ column that the sequence (SERIAL)
is on. This would hide the internal representation of a SERIAL...
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
On Thu, 2003-03-06 at 01:13, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
[ optimizing for small frequent queries ]
What if the client doesn't come back with another query for awhile?
Yup.. Thats why I said you basically lose 1 seconds worth of stats (or
rather can't count on when
On Thu, 2003-03-06 at 11:40, Neil Conway wrote:
On Thu, 2003-03-06 at 09:16, Rod Taylor wrote:
Anyway, the basic proposal would be to change the on / off flags for row
block level into a 'stats delay'. A large number would be off, 0
would have the same properties as today. Default
On Thu, 2003-03-06 at 11:49, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
Not if we expect pg_autovacuum to be able to work. It *needs* this
information.
Why?
The implementation I've had in mind for autovacuum would rely on FSM not
the pg_stats daemon.
FSM as I understand
complaints, as unknown is a rather
common name for constraints :).
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
On Tue, 2003-03-04 at 19:14, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
Might get somewhere by making a special domain thats marked as being
serial, and using that in the column.
I recall some discussion last year about making serial et al. into
domains over int4 and int8
();
if (lasttme currtme)
{
pgstat_report_tabstat();
lasttme = currtme;
}
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
should be easily
retrievable and more portable in most interfaces (jdbc, odbc, etc.).
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
in other ways.
Prevention of the domain from being altered would also help, as you can
then prevent the default from changing.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
is
false.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
to vacuum frequently and have a large FSM. It's
also preferred you do a gradual archival of data and not in bulk.
Archive 10 minutes worth every 10 minutes after 3 days have past rather
than an entire days at once.
On Sunday 02 March 2003 06:35 pm, Rod Taylor wrote:
On Sun, 2003-03-02 at 18:52, Mark
a little trickier -- but
still easily doable.
The most important question is the maintenance window.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
, 2003-03-01 at 02:03, Rod Taylor wrote:
On Sat, 2003-03-01 at 00:44, Stephan Szabo wrote:
On 1 Mar 2003, Rod Taylor wrote:
I'm not sure I understand the question. The case as described simply has
to deadlock because your approaching the same values with conflicting
tasks from opposite
is locked or not, but it's not going to be simple.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
the
table when the larger of 30% or 1000 rows has been affected (inserts, or
deletes mostly). That is probably a better solution overall.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
On Thu, 2003-02-27 at 15:02, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
Agreed -- but they're stored on the row themselves. You might be able
to write a function which executes dirty reads on the table and tells
you if the row is locked or not, but it's not going to be simple
operator is
(was?)
'a' = 'A'
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
databases with sequences
(Oracle). PostgreSQL supports both syntaxes already.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
Index: src/backend/commands/sequence.c
===
RCS file: /projects/cvsroot/pgsql-server
of conversion.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
those questions. No to the first, yes to the second.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
after it's
pulled from the DBI drivers. What version of DBI::Pg are you using?
Last time I used it was with DBI::Pg v1.13.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
Require DROP COLUMN CASCADE for a column that is part of a multi-column
index
Do we want the same behaviour for PRIMARY KEY(col1, col2)? CHECK(col1
col2)? etc. as well?
I'm thinking probably...
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description
.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
--
-- PostgreSQL database dump
--
SET autocommit TO 'on';
\connect - rbt
SET autocommit TO 'on';
--
-- TOC entry 2 (OID 2200)
-- Name: public; Type: ACL; Schema: -; Owner: rbt
--
REVOKE ALL ON SCHEMA public FROM PUBLIC
missed.
- pg_catalog.pg_table_is_visible() works on non-table relations
as well, right?
I would assume so, but haven't checked.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
On Sat, 2003-02-15 at 19:49, Ross J. Reedstrom wrote:
On Sun, Feb 16, 2003 at 01:34:34AM +0100, Ian Barwick wrote:
On Sunday 16 February 2003 01:10, Rod Taylor wrote:
I've been debating a mechanism which could build tab completion tables
based on the documentation for a while now
of pages used for VM-level disk caching
Buf: number of pages used for BIO-level disk caching
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
Wow, I never even thought that was possible. Do other db's support that
feature?
Isn't that basically what the current replication kits for Postgresql do
-- via triggers and log tables?
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description
thousands of phone calls, and
have had many conversations which prove that claim false. People
But IBM told me computers are self healing, so if there is a performance
problem should it just fix itself?
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
) and still be able to change the user applications.
I don't mind /usr/X11R6/etc either, but it's not exactly appropriate for
PostgreSQL ;)
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
as good as md5.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
(3) Sign official releases using the PGDG private key, and provide the
signatures on www.postgresql.org along with the packages themselves.
Sounds about right. I'd go as far as to sign release announcements and
security emails as well.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http
to moderator' ability into the comments area about a
specific comment and that may become a bit easier.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
change of tossing in a periodic VACUUM or would that throw off the
results?
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
if comments are ordered by rating.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
(fail), then beefing it up where available may be useful --
but otherwise it's just additional code.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
substr($2, 1, 3) as schpat, substr($2, 3, 5) as propat)
as t
WHERE p.prorettype 'pg_catalog.cstring'::pg_catalog.regtype
) AS tt,
(SELECT $1 AS cmd) AS cmd
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message
and cannot compile it. gram.y
errors complaining: invalid character: ','.
bash-2.05b$ bison --version
bison (GNU Bison) 1.75
Written by Robert Corbett and Richard Stallman.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally
'pg_catalog.cstring'::pg_catalog.regtype
) AS tt,
(SELECT $1 AS cmd) AS cmd;
ERROR: Parameter '$1' is out of range
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
, 7.6 can remove Guc.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
archives?
http://archives.postgresql.org
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
db gets commands for new db)
but translations for column headers, etc. will be wonky as they're still
tied to psql.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
? .deps
? .describe.c.swp
? psql
Index: command.c
those values?
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
;
This is a far more portable method.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
the client -- but I think they can be discovered from
the context of the variable use instead (Neil?).
Anyway, it's just a thought. psql in 7.4 is free game due to the
anticipated protocol change which will make prior versions
non-functioning anyway.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http
as
it's guarenteed not be to dropped. If we create an ALTER TYPE command
this changes. Do we kill a syscache lookup to prevent the lock --
probably not -- but it makes the above mentioned AccessShareLock count
much larger.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
:
micro_version=`echo $VERSION | sed
's/^[0-9]*\.[0-9]*\.\([0-9]*\).*/\1/;t LABEL
s/.*//;q
:LABEL
s/.*\(\)$/\1/'`
For some reason my sed isn't liking the semicolons.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally
.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
+--
192.168.1.0/24 | 192.168.1.226/24
! 192.168.1.0/24 | 192.168.1.226
! 192.168.1.0/24 | 192.168.1.0/24
192.168.1.0/24 | 192.168.1.0/25
+ 192.168.1.0/24 | 192.168.1.255/24
192.168.1.0/24 | 192.168.1.255/25
(6 rows)
set enable_seqscan to on;
--
Rod
* from inet_tbl where i'192.168.1.0/24'::cidr;
c|i
+--
192.168.1.0/24 | 192.168.1.0/25
192.168.1.0/24 | 192.168.1.255/25
192.168.1.0/24 | 192.168.1.226
(3 rows)
On Wed, 2003-01-15 at 14:58, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED
With Bruce's patch came a few others -- plus a recompile with all
updates.
... and that's the expected result. So why'd you get a different result
while running the regression test? Curiouser and curiouser...
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
On Wed, 2003-01-15 at 15:29, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
With Bruce's patch came a few others -- plus a recompile with all
updates.
Which patch exactly? The regression test was still passing for me
as of yesterday's sources plus the large planner commit I just
On Wed, 2003-01-15 at 16:07, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
Last update was about 5 minutes after Bruce's header fix went into
place.
Hm. I just finished verifying that CVS tip builds and passes cleanly
on both HPUX and Linux (Red Hat 8.0). So either you've got
On Wed, 2003-01-15 at 20:15, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
On Wed, 2003-01-15 at 16:07, Tom Lane wrote:
Hm. I just finished verifying that CVS tip builds and passes cleanly
on both HPUX and Linux (Red Hat 8.0). So either you've got a build
error (did you do a make
:92: warning: parameter has incomplete type
/usr/include/arpa/inet.h:96: warning: parameter has incomplete type
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
) rather than strictly a user.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
On Tue, 2003-01-14 at 17:11, Bruce Momjian wrote:
Any idea what it needs? What is in inet.h at that line, and where is it
defined? I see sys/socket.h included. Does sys/types.h help?
---
Rod Taylor wrote
simply the underlying SQL.
It would be a wise idea to use the INFORMATION_SCHEMA where possible for
these, as that is pretty much guaranteed to be static in format.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed
(and how many) databases will this command work on? Only
the current one? All of them?
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
(not as attachements) - did you
change something?
Not that I know of.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
of the command.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
On Thu, 2003-01-09 at 10:42, Peter Mount wrote:
On 9 Jan 2003, Rod Taylor wrote:
On Thu, 2003-01-09 at 10:12, Justin Clift wrote:
Bruce Momjian wrote:
snip
Let's suppose I am writing a query, and then I do \e to edit the query,
and I exit the editor and return to psql. Suppose
someone can offer an explanation, I am inclined to just supply an
empty table and check off this item.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
in the
interium ... another reason not to announce it right away :)
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
Will advocacy, gborg, archives, techdocs, etc. be updated to
include links back to the portal site?
Don't they already?
If they do, it's not obvious. I don't see anything on archives,
advocacy, or gborg. It looks like techdocs goes to the users lounge
(PostgreSQL Home).
--
Rod Taylor
the attached.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
. Subsequent tuples will simply use the pre-cooked
tree.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
On Tue, 2002-12-17 at 18:15, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
3. On initial pass, CoerceToDomain will have a 'raw' expression tree
(simple arg of data to coerce). After passing through
ExecCoerceTypeConstraints a 'cooked' expression tree will contain the
constraint
).
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
On Wed, 2002-12-11 at 19:00, Bruce Momjian wrote:
It is an idea if no better one can be found, unless we don't want ALTER
DOMAIN at all, which doesn't seem good.
I'll make a proposal for 'Object' locks as suggested, and we'll see
where we go from there.
--
Rod Taylor [EMAIL PROTECTED]
PGP
On Wed, 2002-12-11 at 00:05, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
On Tue, 2002-12-10 at 22:56, Tom Lane wrote:
relation's pg_class row. We have no such locks on types at present,
but I think it may be time to invent 'em.
I'd be happy to use them once created.
I think
what I've seen) isn't an issue. Strictly disk. The
big problem with multiple vacuums is determining which tables are in
common areas.
Perhaps a more appropriate rule would be 1 AVD per tablespace? Since
PostgreSQL only has a single tablespace at the moment
--
Rod Taylor [EMAIL PROTECTED
On Tue, 2002-12-10 at 12:00, Greg Copeland wrote:
On Tue, 2002-12-10 at 08:42, Rod Taylor wrote:
Not sure what you mean by that, but it sounds like the behaviour of my AVD
(having it block until the vacuum command completes) is fine, and perhaps
preferrable.
I can easily
it should be enforcing at the moment.
Thanks for the explanations. I'll see if I can 1) fix my poor knowledge
of locking, 2) Add to my notes that I need to test stuff with Rules from
now on, and 3) correct the above items.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
On Tue, 2002-12-10 at 22:56, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
2. Insufficient locking, guise 2: there's no protection against someone
else adding a column or table while you're processing an ALTER DOMAIN,
either. This means that constraint checks will be missed
Does anybody know where I can find a newer DBD::Pg module for Windows
NT? The only pre-compiled one I can find is 0.98, which is based on a
PostgreSQL 7.0 library set.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed
(1 row)
a=# rollback;
ROLLBACK
a=# select nextval('test');
nextval
-
52
(1 row)
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
they have someone they can go after, who are they going to
go after if PostgreSQL fails them? Marc? Bruce?
This is when you start to shout that RedHat offers commercial support,
licencing, etc. INCLUDING a free, non-restrictive source licence to the
core components of RHDB.
--
Rod Taylor
.
I have read through all the docs/faqs I can find and still have no good
idea about this.
Take a look at the 'System Catalog' documentation, and in psql the -E
option will show you the 'system' queries used to retrieve the
information for display in psql.
--
Rod Taylor [EMAIL PROTECTED]
PGP
for every column in my select. I
say that because it contains a join of pg_class and pg_attribute.
Something like that I would suspect.
But if they're arbitrary selects, how are you going to handle:
SELECT CAST(32 AS text);
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
On Fri, 2002-12-06 at 11:04, Tom Lane wrote:
Joe, have you heard of a standard called SQL/MED? I came across a
It's that one of the later parts of the SQL 99 spec? Section 9 or
thereabouts?
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description
On Fri, 2002-12-06 at 11:35, Rod Taylor wrote:
On Fri, 2002-12-06 at 11:04, Tom Lane wrote:
Joe, have you heard of a standard called SQL/MED? I came across a
It's that one of the later parts of the SQL 99 spec? Section 9 or
thereabouts?
Note to self, don't reply to emails and have
Thanks. I guess I should rename my thread to 7.4 - TODO : allow
constraint names when using the ALTER TABLE table ADD FOREIGN KEY
syntax.
You can do that now.
ALTER TABLE table ADD CONSTRAINT const FOREIGN KEY
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
501 - 600 of 934 matches
Mail list logo
