That I know. That syntax is radically different from that proposed.
Isn't it identical? The CONSTRAINT const is SQL standard optional clause
for all commands that add constraints.
Not to mention the same as the CREATE TABLE syntax for constraints that
we already have.
--
Rod Taylor
and cooked_default it seems.
Thanks,
Chris
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
--
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
On Wed, 2002-12-04 at 12:22, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
cms=# CREATE TABLE foo(bar int);
CREATE
cms=# SELECT * from foo where bar=1.7;
This is a numeric to integer coercion, which rounds
No, it's an integer to numeric promotion (the var is promoted
and you can't use UPDATE on a sequence.
Hackers: Could this be a TODO item for 7.4?
I'm hoping to do that one sooner than later, unless Neil beats me to it.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message
Copy is another story all together. But I'd like a
CREATE SCHEMA ... AS COPY schemaname;
Wouldn't it be better to use pg_dump/pg_restore for that?
Perhaps.. But I'd really like to see some of these types of abilities
added to pg_admin.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key
template1=# select text(2.000::numeric);
text
---
2.000
(1 row)
The text(numeric) function doesn't round numbers. :(
This is bug or feature? :)
I'd say feature in that it doesn't reduce the precision of the number.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca
We could even stop printing that annoying NOTICE ;-)
Agreed with this part :)
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
--+-+--+---+++--+-+---+--++--+--++---+--++-
1247 | typname | 19 |-1 | 64 | 1
|0 | -1 |-1 | f| p | f
| i| t | f | f| t
| 0
(1 row)
--
Rod Taylor [EMAIL PROTECTED]
PGP Key
like round still exists to me.
rbt=# select round('2.4555', 2);
round
---
2.46
(1 row)
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
thing in adding
a nullness bit.
On a new table, there are no rows to check, so alter table is almost
free. Likewise, we can add type checks to see if the type allows null,
skipping the table constraint if this is the case.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
properly track their dependencies) but everything else should be able
to.
Copy is another story all together. But I'd like a
CREATE SCHEMA ... AS COPY schemaname;
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message
has to clean up? Why
don't we introduce: max_fsm_pages = auto or something?
I assume it uses shared memory, so I doubt it's very easy to increase on
the fly -- without having to reduce something else anyway.
--
Rod Taylor [EMAIL PROTECTED]
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
We need contrib/array in 7.4 and unique name in pg_constraint
Whelp. I'd like to make the constraint name unique too, but how do you
coax everyone into renaming their existing constraints -- especially
when there isn't an ALTER CONSTRAINT ... RENAME type statement?
--
Rod Taylor [EMAIL
was lost. Attempting reset: Failed.
Yow!
I believe these are fixed in the patch I sent in last week.
--
Rod Taylor [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
was lost. Attempting reset: Failed.
Yow!
I believe these are fixed in the patch I sent in last week.
--
Rod Taylor [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
statement. It takes five statements.
It's something I'd like to see added as well.
--
Rod Taylor [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
On Sat, 2002-11-30 at 21:22, bpalmer wrote:
Is someone keeping a hopeful todo list?
Nearly every one of the items brought up could / should be on the
standard todo list.
http://developer.postgresql.org/todo.php
--
Rod Taylor [EMAIL PROTECTED]
signature.asc
Description: This is a digitally
On Sat, 2002-11-30 at 23:02, Bruce Momjian wrote:
Rod Taylor wrote:
-- Start of PGP signed section.
On Sat, 2002-11-30 at 21:22, bpalmer wrote:
Is someone keeping a hopeful todo list?
Nearly every one of the items brought up could / should be on the
standard todo list.
http
| Modifiers
+--+---
col| r|
rbt=# alter table ar add primary key (col);
ERROR: Existing attribute col cannot be a PRIMARY KEY because it is
not marked NOT NULL
--
Rod Taylor [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5
)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
--
Rod Taylor [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so
I think it's great - but don't quote me on that. :)
PostgreSQL. Because life's too short to learn Oracle.
PostgreSQL. For those with more to do than babysit a database.
--
Rod Taylor [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4
, then alter in the default.
--
Rod Taylor [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
completely
forgotten about it.
Sorry. Could someone bump CATALOG_VERSION_NO?
--
Rod Taylor [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Thu, 2002-11-21 at 14:11, Bruce Momjian wrote:
Of course, those would be SQL purists who _don't_ understand
concurrency issues. ;-)
Or they're the kind that locks the entire table for any given insert.
--
Rod Taylor [EMAIL PROTECTED]
---(end of broadcast
On Thu, 2002-11-21 at 15:09, scott.marlowe wrote:
On 21 Nov 2002, Rod Taylor wrote:
On Thu, 2002-11-21 at 14:11, Bruce Momjian wrote:
Of course, those would be SQL purists who _don't_ understand
concurrency issues. ;-)
Or they're the kind that locks the entire table for any given
the first table. The sequence was deleted too, leaving the
default of the second table referring to a non-existent sequence.
Could this be a TODO item in 7.4, to add a dependency check when a
sequence is set as the default without being created at the same time?
--
Rod Taylor [EMAIL PROTECTED
On Sat, 2002-11-16 at 15:49, Alvaro Herrera wrote:
On Fri, Nov 15, 2002 at 11:43:47AM -0500, Rod Taylor wrote:
Below is a summary of what pg_depend tracks that might be useful.
Skipped a number of dependencies that are internal only (ie. toast table
dependencies
On Wed, 2002-11-13 at 23:37, Philip Warner wrote:
At 02:53 PM 13/11/2002 -0500, Rod Taylor wrote:
I can make a complete list tonight of whats captured.
Sounds good
Below is a summary of what pg_depend tracks that might be useful.
Skipped a number of dependencies that are internal only (ie
::= column name
path column ::= column name
cycle mark value ::= value expression
non-cycle mark value ::= value expression
--
Rod Taylor [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive
TruncateRelation into cluster.c.
PreCommit_on_commit_actions() - ONCOMMIT_DELETE_ROWS is the only
location using heap_truncate(). It may be possible to change this and
remove heap_truncate() altogether.
--
Rod Taylor [EMAIL PROTECTED]
---(end of broadcast
that, but if I change number of column I want that
'create or replace view' do 'drop view ..; create view ..;'
Why not ?
Now you've just broken all functions, views, rules, and triggers that
depend on that view to function.
--
Rod Taylor
---(end of broadcast
On Wed, 2002-11-13 at 09:08, Philip Warner wrote:
At 08:52 AM 13/11/2002 -0500, Rod Taylor wrote:
The biggest trick will be trying to re-combine the ALTER ... ADD
CONSTRAINT and ALTER ... SET DEFAULT statements back into CREATE TABLE
I'm not sure this would be worth the effort - I'll grant
OR REPLACE FUNCTION func ... 'real query' LANGUAGE 'sql';
So it looks like the only contentious item might be table attrs? is that right?
More likely to be functions. As everything else (I can think of) is
easily altered into place.
--
Rod Taylor
---(end of broadcast
derived column ::=
value expression [ as clause ]
as clause ::= [ AS ] column name
But this isn't going to be very nice to fix.
conflicts: 1378 shift/reduce, 44 reduce/reduce
--
Rod Taylor
---(end of broadcast)---
TIP 2: you can
+--+-+--
public | d| integer | not null
public | f| text|
(2 rows)
Any thoughts on how to display the check constraints?
--
Rod Taylor
---(end of broadcast)---
TIP 2: you can get off all lists at once
(VALUE BETWEEN 6 AND 10);
SELECT CAST(8 AS dom);
--
Rod Taylor
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
On Mon, 2002-11-04 at 09:44, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
Is it safe to teach Var how to deal with values that do not originate
from a tuple? Or should I create a new primnode to deal with these
types of variables.
I have no idea what you're talking about
gmake[1]: Leaving directory `/usr/local/pgsql/beta/pgsql/doc/src/sgml'
gmake: *** [postgres.tar] Error 2
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
--
Rod Taylor
make sure whatever it is execs a background jobs (commits are held
during execution of the script) and protect against simultaneous runs of
the background job.
Rod Taylor
---(end of broadcast)---
TIP 6: Have you searched our list archives
and earlier did not support such syntax.
--
Rod Taylor
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
I know this, the question is, Should this happen? If not, can we fix it
somehow?
Or do we need to put a note somewhere?
I think it's a little late to fix now.
Making psql support multiple versions was a suggestion Tom made a while
back, but nobody took up the challenge.
--
Rod
On Fri, 2002-11-01 at 14:18, Larry Rosenman wrote:
On Fri, 2002-11-01 at 12:25, Rod Taylor wrote:
I know this, the question is, Should this happen? If not, can we fix it
somehow?
Or do we need to put a note somewhere?
I think it's a little late to fix now.
Making psql
are
particularly likely to fail if the server is of a different version.
However, perhaps this version is worthy of a remark in the release notes
with the schema description:
Non-schema aware versions of the utilities distributed with PostgreSQL
to be 100% functional with PostgreSQL = 7.3.
--
Rod
that table.
However, I can see a good argument to allowing running the constraints
as the user who created the constraint. This means would require
tracking of constraint ownership.
--
Rod Taylor
---(end of broadcast)---
TIP 5: Have you checked our
On Thu, 2002-10-31 at 10:33, Bruno Wolff III wrote:
On Thu, Oct 31, 2002 at 10:17:26 -0500,
Rod Taylor [EMAIL PROTECTED] wrote:
Can't necessarily run them as the table owner, as it may give
information to other users with the ability to ALTER that table.
You have to be the table owner
thing I think we should do in any case is improve
the wording of the error message.
Got a suggestion?
Change: RelationClearRelation: relation 25172 deleted while still in use
to: RelationClearRelation: a relation (id: 25172) was deleted while still
in use
--
Rod Taylor
On Thu, 2002-10-31 at 13:03, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
Found another:
ERROR: cannot find attribute 2 of relation pg_temp_12100_0
Can you reproduce that?
It could be that this just represents someone's temp table deletion
committing while VACUUM is partway
truncated.
--
Rod Taylor
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
On Wed, 2002-10-30 at 15:38, Neil Conway wrote:
Rod Taylor [EMAIL PROTECTED] writes:
ERROR: RelationClearRelation: relation 11584078 deleted while still in
use
I was going to report a similar error that arises in a different
situation:
Probably a different look at the same problem
://archives.postgresql.org
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
--
Rod Taylor
---(end of broadcast)---
TIP 1
if they actually try to use PostgreSQL to get at the data.
There are a couple of tools which were designed to recover database data
while the db is not running.
--
Rod Taylor
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL
= 'a'::character varying) AND (i1 = 'b'::character varying))
I think you typo'd. i1='a' AND i1='b' turns into 'a' = 'b' which
certainly isn't true in any alphabets I know of.
--
Rod Taylor
---(end of broadcast)---
TIP 5: Have you checked our
?
http://archives.postgresql.org
--
Rod Taylor
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
10Mb fixed length datatype -- how about a huge array of
integers if the previous are considered blobs?)
--
Rod Taylor
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
.
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
--
Rod Taylor
---(end of broadcast
On Wed, 2002-10-09 at 14:04, Justin Clift wrote:
Rod Taylor wrote:
snip
Oh, if thats your problem then use asynchronous replication instead.
For specific info, the contrib/rserv package does master-slave
Thanks. I was having a heck of a time remembering what it was called or
even
it ...
Wow Tom! That's wonderful! On the other hand, maybe people needed the
extra idle CPU time that was provided by the unpatched code. ;)
Naw. Distributed.net finally got through RC5-64. Lots of CPU to spare
now.
--
Rod Taylor
---(end of broadcast
of..), but why does it pick Tuesday?
--
Rod Taylor
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
On Sat, 2002-09-28 at 16:38, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
Leaving a zero-width table would be best, even if its not so useful. I
don't like rejecting a CASCADE as it kinda defeats the purpose of having
CASCADE.
I did something about this --- as of CVS tip, you
worth.
--
Rod Taylor
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
triggers.
If this type of stuff has to be done, then this is probably the best way
to go.
--
Rod Taylor
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Is this the only problem that 7.0 people are going to experience (server
side, SQL changes are abundant)?
You're missing the point. Welche was upgrading *from 7.2*. But his
trigger definitions had a dump/reload history going back to 7.0.
Oh.. I certainly did.
--
Rod Taylor
a sequence of commands that can reproduce this?
--
Rod Taylor
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
needs to implement a background fsck that will run on a
mounted filesystem.
--
Rod Taylor
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
On Thu, 2002-09-26 at 17:47, Bruce Momjian wrote:
Rod Taylor wrote:
Yes, before UFS had soft updates, the synchronous nature of UFS made it
slower than ext2, but now with soft updates, that performance difference
is gone so you have two files systems, ext2 and ufs, similar peformance
])
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
--
Rod Taylor
---(end
unique indexes into unique constraints.
As I had a few items I didn't want to upgrade, it asks the user if they
want to do each one (-Y to fix 'em all).
--
Rod Taylor
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http
;
ANALYZE
rbt=# commit;
COMMIT
rbt=# create function test() returns bool as 'analyze; select true;'
language 'sql';
CREATE FUNCTION
rbt=# select test();
test
--
t
(1 row)
--
Rod Taylor
---(end of broadcast)---
TIP 6: Have you searched our list
works
perfectly fine for that.
--
Rod Taylor
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
On Mon, 2002-09-16 at 17:54, Tom Lane wrote:
In CVS tip:
regression=# create domain nnint int not null;
CREATE DOMAIN
Ok, I'll take a look at this today.
Thanks
--
Rod Taylor
---(end of broadcast)---
TIP 1: subscribe and unsubscribe
is available now, so it shouldn't be much of an
issue.
--
Rod Taylor
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
/upgrade.shtml
Doesn't deal with DEFERRED triggers.
--
Rod Taylor
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
some people don't like?
--
Rod Taylor
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
in the referenced table.
--
Rod Taylor
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
? I've done this one a number of
times through views to log the user pulling out information from the
system, and what it was at the time (time sensitive data).
--
Rod Taylor
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
at transaction commit, and re-created in next use.
4.29:
For every declare cursor in an SQL-client module, a cursor is
effectively created when an SQLtransaction (see Subclause 4.32,
SQL-transactions ) referencing the SQL-client module is initiated.
--
Rod Taylor
---(end
.
Rod Taylor
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
the dependencies, then drop the column the view
continues to function but I'm not sure thats always the case.
--
Rod Taylor
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
, nothing gets
better.
I suspect it'll be several more major releases before we begin to
consider it approaching completely functional.
--
Rod Taylor
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
push and put in the work
require it'll eventually go where you want it to.
--
Rod Taylor
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
;
ERROR: current transactions is aborted, queries ignored until end of
transaction block
snpe rollback;
ROLLBACK
snpe select * from org_ban;
Maybe I'm missing something, but isn't that the expected behaviour when
autocommit is turned off?
--
Rod Taylor
---(end
have
INSTEAD triggers or contraints.
Well.. Triggers could be exclusively INSTEAD. A trigger could easily
write a few things to a number of other tables, and return NULL in a
BEFORE trigger which would prevent execution of the requested command.
--
Rod Taylor
---(end
On Fri, 2002-09-06 at 01:19, Christopher Kings-Lynne wrote:
OK,
The argument about using ALTER TABLE/ADD FOREIGN KEY in dumps was that it
caused an actual check of the data in the table, right? This was going to
be much slower than using CREATE CONSTRAINT TRIGGER.
So, why can't we do
On Wed, 2002-09-04 at 22:39, Marc G. Fournier wrote:
will announce it on -announce tomorrow, if ppl want to take a quick look
at it ... man pages weren't included, but I did regenerate the docs per
Peter's suggested commands ...
'./configure make check' passes on i386 FreeBSD.
SunOS
On Thu, 2002-09-05 at 11:19, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
SunOS control.shared2 5.7 Generic_106541-20 sun4u sparc SUNW,Ultra-5_10
shows an error in ALTER TABLE tests:
ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1) references
pktable(ptest1);
NOTICE: ALTER
In the process of upgrading a few systems for the Beta, I ended up
writing a tool to upgrade the Foreign key, Unique, and Serial objects to
their 7.3 version from the 7.2 version (may work on prior -- but not
guarenteed).
I imagine it'll fail miserably on mixed case, or names with spaces --
but
of requests.
On Thu, 2002-09-05 at 21:37, Christopher Kings-Lynne wrote:
Whoot! I was just thinking about writing such a tool. Thanks.
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Rod Taylor
Sent: Friday, 6 September 2002 12:38 AM
Found this line without a name:
Propagate column or table renaming to foreign key constraints
Is that item complete? pg_constraint follows (as such dump / restore
will work) but the triggers themselves still break, don't they?
On Wed, 2002-09-04 at 03:24, Bruce Momjian wrote:
OK, the HISTORY
It would be far simpler to put each of the core teams names on the top
of the history file in big bold letters -- or perhaps a watermark in the
background ;)
While we're competing for the humble award, you might want to add Tom to
that list...
---(end of
On Tue, 2002-09-03 at 03:36, Mario Weilguni wrote:
gets updated for each transaction but log table is just an insert. So
rather
than vacumming entire db, just doing 'vacuum analyze accounts' give me
almost
same results.
That is not really practicable, one datebase has 107 tables, and
On Tue, 2002-09-03 at 11:01, Tom Lane wrote:
Shridhar Daithankar [EMAIL PROTECTED] writes:
1)Is this sounds like a workable solution?
Adding a trigger to every tuple update won't do at all. Storing the
counts in a table won't do either, as the updates on that table will
generate a huge
Seems it wants to run a redo entry that doesn't exist.
Not a big deal as it's a test environment only. It was recently
upgraded from 7.2.1 to 7.2.2. I'm wondering whether the person who did
the upgrade shutdown the daemon before installing.
FATAL 1: The database system is starting up
FATAL
On Tue, 2002-09-03 at 16:42, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
DEBUG: server process (pid 9097) was terminated by signal 10
Could we have a backtrace from that core dump?
AFAICT it's getting through the WAL redo just fine, so the problem
is (probably) not what you
On Mon, 2002-09-02 at 02:36, Christopher Kings-Lynne wrote:
Whatver happened to Rod's work on the BETWEEN command? I remember he got to
the stage of realising a lot of execetor changes had to be made...?
I've not had time to implement the optimizer portion.
---(end
* Have SERIAL generate non-colliding sequence names when we have
auto-destruction
They should be pretty well non-colliding now. What's the gripe exactly?
The issue was that when there were name collisions, we threw an error
instead of trying other sequence names. We had to do
Oops, my fault for being imprecise.
I was wondering what time of day with timezone. Someone suggested end of today
but that means different times to different people.
This is what Marc said yesterday:
Yup, I believe that it is the case that both the US and Canada
celebrate
labour day on
One more idea, is it possible to fake a read-write file system. I.e.
supply the files that postgresql will be looking for? (I know it's a
stretch, but hey, this IS the hackers list) :)
One of the tricks I use for diskless systems is to mount a ramdrive in a
union mount with a read only nfs
On Wed, 2002-08-28 at 10:24, Robert Treat wrote:
On Wed, 2002-08-28 at 10:11, Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Larry Rosenman wrote:
Why? If both old and new are acceptable, why not document it?
(Just curious, I'm not wedded to it).
Well, showing both
Yes, I thought about that. People want to show both SELECT syntaxes,
but how would you do that --- show the SELECT syntax twice with just
those last two clauses reversed --- yuck.
select [ stmt group, ... ]
stmt group :
[ FOR UPDATE | LIMIT ]
The above, or something along those
601 - 700 of 934 matches
Mail list logo
