resql.org/pgsql-hackers/2008-06/msg00102.php
... mentions keeping collation information together with text data,
however it is referring to keeping it together when processing it,
not when storing the text.
Regards,
Stephen Denne.
--
At the Datamail Group we value teamwork, respect, achievement, client
urrent postgresql.
However variations on this kind of daemon can be used to perform testing,
configuring it to work well, go slow, pause, not respond, disconnect, or fail
in particular ways, emulating disk full, etc.
Regards,
Stephen Denne.
--
At the Datamail Group we value teamwork, respect, achievem
html
Which says
"Checking of constraints that are deferrable can be postponed until the end of
the transaction"
and
"If the constraint is INITIALLY DEFERRED, it is checked only at the end of the
transaction."
I'd also contest this statement:
"Only foreign key c
function is being called for the
first time in a transaction. You don't know when to clear it.
Regards,
Stephen Denne.
Disclaimer:
At the Datamail Group we value team commitment, respect, achievement, customer
focus, and courage. This email with any attachments is confidential and may be
> The big gotcha is that these are all non-transactional
> : if you rollback,
> GD and SD stay the same, and when you issue a query, you can
> assume the
> state of SD and GD is random (due to previous queries) unless you
> initialize them to a known value.
Using txi
SD and GD, private and public. Where
are the context boundaries?
Regards,
Stephen Denne.
Disclaimer:
At the Datamail Group we value team commitment, respect, achievement, customer
focus, and courage. This email with any attachments is confidential and may be
subject to legal privilege. If it is
Tom Lane wrote
> Transaction commit is an exceedingly subtle and carefully structured
> thing. Throwing random user-defined code into it ain't gonna happen.
Deferred constraint triggers currently run random user-defined code. This'll do
me.
Regards,
Stephen Denne.
Disclaimer:
Tom Lane wrote
> "Stephen Denne" <[EMAIL PROTECTED]> writes:
> > From: Tom Lane [mailto:[EMAIL PROTECTED]
> >> As for 2) and 3), can't you look into the pg_settings view?
>
> > pg_settings view doesn't contain custom variables created
> on
pes than just text), which I presume would
appear in pg_settings.
Updating existing variables is much quicker, over 10 updates per second.
Regards,
Stephen Denne.
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Wed 16/04/2008 1:55 p.m.
"Stephen Denne&q
(There is a possible performance bug mentioned at the end of the email, the
rest is further discussion regarding materialised views)
I wrote
> Pavan Deolasee wrote
> > On Thu, Mar 20, 2008 at 3:24 AM, Stephen Denne
> > <[EMAIL PROTECTED]> wrote:
> >
> > >
oblem, since again it only works if the COPY
> command gets to execution.
It is only now that I've found the \set ON_ERROR_STOP command, which I presume
would have solved my problem.
Regards,
Stephen Denne.
Disclaimer:
At the Datamail Group we value team commitment, respect, achievement, customer
Pavan Deolasee wrote
> On Thu, Mar 20, 2008 at 3:24 AM, Stephen Denne
> <[EMAIL PROTECTED]> wrote:
>
> >
> > Pavan also refers to deferred triggers, which has got me
> thinking about another possible solution:
> >
> > Instead of inserting a delta r
ted many times, then on
commit the trigger is fired once, and the temp table is dropped.
Does anyone think this will or won't work for some reason?
Regards,
Stephen Denne.
Disclaimer:
At the Datamail Group we value team commitment, respect, achievement, customer
focus, and courage. This e
Tom Lane wrote
> "Stephen Denne" <[EMAIL PROTECTED]> writes:
> > What I was asking about with those questions, is if a
> > single row is inserted in transaction A, and updated 1000
> > times still within transaction A, then transaction A
> > commits..
(Sorry for the repeat email Tom, I forgot the cc's)
Tom Lane wrote:
> "Stephen Denne" <[EMAIL PROTECTED]> writes:
> > I initially thought that what you meant by "having
> > transactions enter "delta" entries" was that I have a trigger
>
he same benefit from having a trigger set up to fire
pre-commit (or pre-prepare), and be a part of the transaction.
Would the locking difficulties be reduced as the lock would not be required
till late in the game, and not held for long?
Regards,
Stephen Denne.
Disclaimer:
At the Datamail Group
23 and staattnum=2;
I can then pick a number of distinct values such that the effective arithmetic
mean is equal to what I calculated the geometric mean to be.
Stephen Denne.
Disclaimer:
At the Datamail Group we value team commitment, respect, achievement, customer
focus, and courage. Th
like the idea of changing one limit into two limits. Or are you
suggesting changing the algorithm that determines how many, and which pages to
analyze, perhaps so that it is adaptive to the results of the analysis as it
progresses? That doesn't sound easy.
Regards,
Stephen Denne.
d if determined to be significantly different from the arithmetic mean,
stored in a new stats column. When estimating the number of rows that will be
returned by queries of the form shown above, if there is a geometric mean
stored, use it instead of the arithmetic mean.
Regards,
Stephen Denne.
get should result in more pages
being read, and a more accurate record of statistics. It shouldn't result in
significantly more work for the planner.
It wouldn't solve my problem though, which is frequent over-estimation of rows
when restricting by this field with values not known at plan tim
;t have bothered creating any indexes on wooper.
Regards,
Stephen Denne.
Disclaimer:
At the Datamail Group we value team commitment, respect, achievement, customer
focus, and courage. This email with any attachments is confidential and may be
subject to legal privilege. If it is not intended for you
wooper_seqnumber desc limit 1
),'No Operation Completed') as LastFinshedOp
regards,
Stephen Denne.
Disclaimer:
At the Datamail Group we value team commitment, respect, achievement, customer
focus, and courage. This email with any attachments is confidential and may be
subject to legal pr
(Queries include predicates of the form [indexed text expression] like "ABC%")
Stephen Denne
Disclaimer:
At the Datamail Group we value team commitment, respect, achievement, customer
focus, and courage. This email with any attachments is confidential and may be
subject to legal priv
t should perhaps be larger than 4.0? Would that make the second
estimate larger than the first estimate?
Stephen Denne.
Disclaimer:
At the Datamail Group we value team commitment, respect, achievement, customer
focus, and courage. This email with any attachments is confidential and may be
su
of magnitude faster for me.
Stephen Denne.
Disclaimer:
At the Datamail Group we value team commitment, respect, achievement, customer
focus, and courage. This email with any attachments is confidential and may be
subject to legal privilege. If it is not intended for you please advise by
reply imme
is only
happening when running both v8.2 and v8.3rc1 at once, and I think it is the
second started that is missing the process descriptions.
Regards,
Stephen Denne.
Disclaimer:
At the Datamail Group we value team commitment, respect, achievement, customer
focus, and courage. This email with any att
Jeff Davis wrote
> > Well clusteredness is used or could be used for a few
> different heuristics,
> > not all of which this would be quite as well satisfied as
> readahead. But for
>
> Can you give an example? Treating a file as a circular structure does
> not impose any significant cost that I
ed for 8.2.
PostgreSQL is started as a service.
Stephen Denne
Disclaimer:
At the Datamail Group we value team commitment, respect, achievement, customer
focus, and courage. This email with any attachments is confidential and may be
subject to legal privilege. If it is not intended for you please
28 matches
Mail list logo
