d uniqueness,
etc, but might also well think of a given attribute as the primary key.
Use of constraints in lieu of "primary key" come to mind...
'Course, maybe I missed the point! -smile-
'Nother thought: CYA _can_ have odeous performance costs if
over-implemented. It's a
ule changes are designed to support exactly that
> in a 100% backward compatible way.
>
> Jan
Fantastic! ...At some point you'll be thinking of the management end -
turning it on or off, etc. That might be where these other points come
more into play.
Richard
--
Richard Troy, Chief Scient
On Fri, 9 Feb 2007, Andrew Dunstan wrote:
> Richard Troy wrote:
> > In more specific terms, and I'm just brainstorming in public here, perhaps
> > we can use the power of Schemas within a database to manage such
> > divisions; commands which pertain to replication can/
ng mechanism that most everyone is
familliar with. While there are/may be database-wide, nay, installation-
wide constructs as in your Commit Timestamp proposal, I don't see that
there's any conflict - at least, from what I understand of existing
systems and proposals to date.
HTH,
Richard
--
R
p now and then might be helpful to your public disposition.
-smile-
peace,
Richard
--
Richard Troy, Chief Scientist
Science Tools Corporation
510-924-1363 or 202-747-1263
[EMAIL PROTECTED], http://ScienceTools.com/
---(end of broadcast)---
TIP 6: explain analyze is your friend
resting cases would like to and the
entire community is better served if the various "solutions" are in
harmony.
Richard
--
Richard Troy, Chief Scientist
Science Tools Corporation
510-924-1363 or 202-747-1263
[EMAIL PROTECTED], http://ScienceTools.com/
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
ening the named file does not exist at all in the
> > program, or that it's conceptually impossible."
>
> Uh, I think you might be reading the diff backwards. The current CVS
> wording is "cannot".
No, Bruce, he got it exactly right: "cannot" indicates
them, in effect, "No, I don't want
you to have to spend any of your machine's performace giving you the
information you need?"
Help your user by giving them information when they want it. ... Do you
argue that this is useless information?
Richard
--
Richard Troy, Chief Scientis
tements.
Further, in my experience, DDL statements are very carefully thought
through and are usually either completely automated by well crafted
programs or are performed by one person at a time - the DBA. I therefore
conclude that any deadlock risk is triflingly small and would be a
self-inflicte
m... "will need" ... Have you prototyped this system yet? ISTM you can
prototype your proposal using "external" components so you can work out
the kinks first.
Richard
--
Richard Troy, Chief Scientist
Science Tools Corporation
510-924-1363 or 202-747-1263
[EMAIL
reasonably well doc'd now, but many are not, and in almost all cases
> it's only plain text not SGML.
+1
> * Better advertising, for instance make the contrib documentation
> available on the website (which probably requires SGML conversion
> to happen first...)
+1
RT
--
h a cursor with an id of some kind that allowed matching up
open/close pairs. I also think that that the documentation should be
updated to not only indicate usage of this new feature, but provide
cautionary warnings about the potential locking issues and, for the
authors of libraries, Java in part
On Mon, 15 Jan 2007, Neil Conway wrote:
> On Mon, 2007-01-15 at 10:51 -0800, Richard Troy wrote:
> > I therefore propose that the engine evaluate -
> > benchmark, if you will - all functions as they are ingested, or
> > vacuum-like at some later date (when valid data
al in short
order and be improved with time so all the work doesn't have to be
implemented on day 1. And, DBA/sys-admin tweaking can always be done by
updating the catalogues.
HTH,
Richard
--
Richard Troy, Chief Scientist
Science Tools Corporation
510-924-1363 or 202-747-1263
[EMAIL PROTECTED]
the source code. Best would be in
the official documentation/on a web page.) On occasion, I could *really*
use such a list! (If such already exists, please point me at it!)
Thing is, Tom, not everybody has the same level of information you have on
the subject...
Regards,
Richard
--
Richard Troy, Chief S
a build has failed (including patches)? I'd
think so, especially in a build-farm scenario.
...Just my two cents - and worth every penny! -smile-
Richard
--
Richard Troy, Chief Scientist
Science Tools Corporation
510-924-1363 or 202-747-1263
[EMAIL PROTECTED], http://ScienceTools.com/
-
ronment into
production."
No, unfortunately, I can't volunteer to be the point person on this one.
And to the underlying question: is this the case with PostgreSql? I can't
say...
Regards,
Richard
--
Richard Troy, Chief Scientist
Science Tools Corporation
510-924-13
be done.
>
>Thanks,
>
>Stephen
...I thought you said this _needs_ to be done - by using words like
"unacceptible" and "required" - and I disagree. There's a difference
between what needs to be done and what is desired to be done. Further, I
never said
dvantage that
users can share one authentication.
Unless I've really overlooked something basic, there's nothing lacking in
the existing scheme...
Richard
--
Richard Troy, Chief Scientist
Science Tools Corporation
510-924-1363 or 202-747-1263
[EMAIL PROTECTED], http://Scie
rite it lowercase and wonder
> why it isn't working. :)
>
>
> I agree, we can't make every '\' command case-insensitive, but a few,
> where it makes absolute sense, should be subject to reconsideration. We have
> the choice of making it more user-
could
possibly overwhelm the benefits in high-update scenarios. The point that
each server operates independently is only true if you ignore the the
necessary replication - which, to my mind, links the systems and they are
not independent. ...I suppose that in a completely read-only environment -
or u
th a back door. The real
answer is "probably not!" I'm in that world. I haven't been briefed. Ever.
> And I agree with your point, still. However, that would open a precedent
> for people to have to maintain lists of stable software in every
> documentation area.
All tha
by helping
them find information, especially about things they don't know exist. All
that's needed are pointers, but the pointers need to be to solid
documents/resources, not just the top of a heap - if you'll forgive the
pun.
Richard
--
Richard Troy, Chief Scientist
e
anyway.
While I've never used Oracle's clustering tools, I've read up on them and
have customers who use them, and I think this description of Oracle
clustering is a mis-read on what the Oracle system actually does. A check
with a true Oracle clustering expert i
?) on whatever, and we need a rebuttal ready at hand or
they'll go with Oracle. We just don't have the time to fight that battle,
nor do we wish to risk the sale when we can work with Oracle just fine.
In sum, I agree with Tom Lane and the others who chimed in with "
25 matches
Mail list logo
