Andreas Pflug <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> This can already be done by comparing old and new values, no?
>>
> No, this is not the case.
> UPDATE foo SET x=x, y=y
> is different from
> UPDATE foo SET y=y
> if triggers maintaining x are involved.
Only for what I would call extr
On 5 Aug 2003 at 9:40, Lamar Owen wrote:
> On Tuesday 05 August 2003 03:15, Shridhar Daithankar wrote:
> > I am willing to build 7.4beta binaries on slackware and upload them
> > someplace. This is just to add to binary packages readily available.
>
> > Can anybody tell me what flags etc. are to
Rod Taylor <[EMAIL PROTECTED]> writes:
> After the first few sleeps should it add a random() element to the delay
> time?
Hmm, that's a thought --- but how big a random element?
Fooling with the original idea, I'm having trouble with getting both
plausible backoff and a reasonable number of attem
I'm using 7.3.3 of the server, and pg73b1jdbc2.jar for the JDBC driver.
Various permutations of calls to the setTransactionIsolation all fail to
yield a driver state that will tell me that it is set up for
serializable transactions.
Help!?
I googled, I grepped. I find mention of problems with
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Adding several new variables is fine, but what do we call the hostname
> > option if we already have log_hostname?
>
> We've renamed GUC variables before for consistency. I'd opt
> for picking names that show the common purpose, ma
> I'm looking over the last bits of translations of pg. Is it to late to
> update the translations for 7.4? Should I work on the cvs head version or
> is there some branching going on?
It's not too late - translations are allowed during beta I think. And yeah,
use cvs HEAD.
Chris
-
Rod Taylor <[EMAIL PROTECTED]> writes:
> How about (round to nearest 10msec):
> time =3D oldtime + oldtime / 2 + oldtime * rand()
> while (time > 1 second)
> time =3D time - 0.80sec
> This would stagger the wakeup times, and ensure a larger number of
> retries -- but the times should be la
I too got this error. This happened with Postgres 7.2.3 and Linux 2.4.20 on via
processor. This happened not on just one box but around dozen boxes. This may not be
hardware problem.
In our case, we create the table and use it then delete it. This activity happens very
often, once a day. we
On Mon, Aug 04, 2003 at 10:47:36AM +0200, Andreas Pflug wrote:
> AFAICS the current implementation still doesn't have a way to access the
> affected rowset, so it'a pretty much like a SELECT without a WHERE.
Yeah, unfortunately I didn't get a chance to implement this functionality
during the 7.4
Hi Magnus,
Thanks for that. I always believed that the mcpu flag could enable a C
compiler to generate code that could use the extra instructions on the
newer CPUs - perhaps one day I'll get around to reading the
documentation ;)
Anyway, I've posted the compiled RH 7.3 postgresql-7.3.4 RPMs at
ht
Bruce Momjian wrote:
Andreas Pflug wrote:
YATS (yet another TODO suggestion):
provide an official and reliable way to temporarily enable/disable triggers.
"ALTER TABLE xxx ENABLE/DISABLE TRIGGER ALL/trgName"
We still have that nasty "not presently checked everywhere it should be"
comment in th
Mike Mascari <[EMAIL PROTECTED]> writes:
> Should there be any correlation between the manner by which the
> backoff occurs and the number of active backends?
If we could guess how many are contending for the same spinlock, maybe
we could use that info ... but I don't see a reasonably cheap way to
Andreas Pflug <[EMAIL PROTECTED]> writes:
> I wonder why you are suggesting workarounds for features that other
> databases provide.
The fact that other databases provide 'em doesn't make them good ideas.
In particular, writing a trigger that assumes that only the fields
changed by the original U
If we're looking at this, we might want to look at how apache does it with
it's customlog feature. This allows you to first define custom log types,
then set them according to which virtual server you're setting up.
I could see that being nice so you could create a couple of different
custom l
The Hermit Hacker writes:
> /usr/bin/cvs -d /cvsroot -q checkout -rREL7_4_BETA1 -P pgsql
> /usr/bin/find pgsql -type d -name CVS -print | xargs rm -rf
While I second the note that you really should be using cvs export, the
second line is redundant in any case, because gmake dist already does
that
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I think we need a more general variable that can take several values,
> separated by commas, like:
> log_line: dbname,user
> or something like that.
Strikes me as overkill --- adding two more booleans comparable to
log_pid would do the job just as
Josh Berkus <[EMAIL PROTECTED]> writes:
> From my perspective, we could really use a "delimiter" between the
> "fields" of log output which is unlikely to appear within those fields
> instead of parsing by character count, rather than making dbname a
> special case.
Well, Andrew was arguing that s
Tom Lane wrote:
Andreas Pflug <[EMAIL PROTECTED]> writes:
Consider this:
Table with one column that is maintained by a trigger for this rule:
- Only one row in a group of rows may have a foo-value of "true", all
others must be "false".
- If foo=true is inserted/updated, other members of that d
Oh, yes. Let me add that. I didn't realize that was a change of enough
significance.
How is this?
Prevent timestamp from supressing ':00' seconds display
---
Larry Rosenman wrote:
> No, the one where we always p
following is taken from postgresql-7.3.2/src/backend/storage/lmgr/readme:
"If we are setting a table level lock
both the blockId and tupleId (in an item pointer this is called
the position) are set to invalid, if it is a page level lock the
blockId is valid, while the tuple
Tom Lane wrote:
Andreas Pflug <[EMAIL PROTECTED]> writes:
- Implement a way to enable triggers to check which columns are affected
by the triggering statement.
This can already be done by comparing old and new values, no?
No, this is not the case.
UPDATE foo SET x=x, y=y
is different fr
Karel Zak <[EMAIL PROTECTED]> writes:
> On Mon, Aug 04, 2003 at 05:03:02PM -0400, Tom Lane wrote:
>> Only if you use a locale that is assuming a character set that is not
>> UTF8 but does have characters with the high bit set. I'm not sure that
>> we can do anything to defend against locale/charse
I've been thinking about Ludwig Lim's recent report of a "stuck
spinlock" failure on a heavily loaded machine. Although I originally
found this hard to believe, there is a scenario which makes it
plausible. Suppose that we have a bunch of recently-started backends
as well as one or more that have
Joe Conway wrote:
Andreas Pflug wrote:
But PostgreSQL may be better than Oracle, don't you think? In the
named document,
MSSQL2000 still doesn't have row level triggers, and I doubt that
2003 has.
Right, so as you've pointed out, Postgres trigger implementation is at
least in some ways mo
Updated. Thanks.
---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > How is this?
> > Prevent timestamp from supressing ':00' seconds display
>
> I think that was type interval, not timestamp.
>
>
It's more work for a very small cosmetic benefit, ISTM. Setting up
atomic GUC variables is trivially easy, I'm happy to say. Not that I
can't write a simple parser, but why bother for something so tiny?
Also, would we be saying (or implying) that the order given on the line
would affect the ou
Bruce Momjian <[EMAIL PROTECTED]> writes:
> How is this?
> Prevent timestamp from supressing ':00' seconds display
I think that was type interval, not timestamp.
regards, tom lane
---(end of broadcast)---
TIP 3: if pos
Alien ( http://kitenet.net/programs/alien/ ) could possibly help you
handle .deb files (depending on your platform).
cheers
andrew
[EMAIL PROTECTED] wrote:
There is a dbf2pg package on debian that appears to have a higher version
number, but I don't know what to do with a .deb file extension
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> Please test and let me know if there are any problems ...
The .gz tarball matches what I have here. Didn't check the .bz2 one.
regards, tom lane
---(end of broadcast)---
TIP 5
Do you have suggested wording?
---
Andreas Pflug wrote:
> Bruce Momjian wrote:
>
> >Here are the changes for 7.4. I am looking for any improvements. This
> >will be adjusted as we move through beta.
> >
> >---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > On a philosophical note, I usually don't add core folks to release items
> > _with_ other folks because we want to encourage non-core contributors,
> > and because there is already the assumption that core is involved in
> > many patch
Will check later today.
Extract from man gcc:
-mcpu=cpu-type
Tune to cpu-type everything applicable about the generated code,
except for the ABI and the set of available instructions. The
choices for cpu-type are i386, i486, i586, i686, pentium,
pentium-
Andreas <[EMAIL PROTECTED]> writes:
> Agreed, workarounds are easy. The original suggestion of "TRUNCATE ALL"
> (or "TRUNCATE table CASCADE"), however, was motivated by the search for a
> simple and efficient truncation of all tables to accelerate unit-testing.
I still think the best suggestion fo
Larry Rosenman writes:
> What the fr*** harm is it in passing -D_REENTRANT into the libpq build on
> UnixWare
> irregardless of the --with-threads* flag?
Indeed for every other sane system out there. Folk are messing around
with the thread stuff using here-say as knowledge. We want to compile
'K ... I just re-tag'd REL7_4_BETA1 for the changes that were made
(including Bruce's last minute copyright changes) ...
Also, I just modified the script so that it builds both a .gz and a .bz2
version of hte archives ...
Please test and let me know if there are any problems ...
Marc G. Fournie
Hi there,
> I agree with Tom ... even the idea of a "TRUNCATE ALL" makes me nervous. If
> we had such a feature, I'd advocate that it be superuser only.
This "superuser only" restriction certainly would be sensible.
> As for "TRUNCATE CASCADE" or similar improvements, I agree that they
could be
Joe Conway wrote:
> Bruce Momjian wrote:
> > Here are the changes for 7.4. I am looking for any improvements. This
> > will be adjusted as we move through beta.
> >
>
> Almost anything with my name on it (but certainly all the array and
> polymorphic function stuff) could have Tom's too, since
On Tue, 5 Aug 2003, Bruce Momjian wrote:
> Oleg Bartunov wrote:
> > Bruce, you forgot new contrib/tsearch2 module - full text extension (Oleg,Teodor)
>
> Sorry, added:
>
> New tsearch2 full-text search module (Oleg)
Bruce, I wrote (Oleg,Teodor)
>
>
Regards,
Oleg
__
On Mon, Aug 04, 2003 at 05:03:02PM -0400, Tom Lane wrote:
> Julian Satchell <[EMAIL PROTECTED]> writes:
> > The implementations of lower and upper in
> > src/backend/utils/adt/oracle_compat.c use the single byte macros from
> > ctype.h to alter individual bytes in the text string.
>
> > If the te
39 matches
Mail list logo
