"Neil Conway" <[EMAIL PROTECTED]> writes:
> Tom Lane said:
>> I'm inclined to preserve that behavior,
>> primarily because not doing so would create a tremendous penalty on
>> applications that expect it to work that way.
> What sort of application are you envisioning?
The ones that have a per-ro
For my part, I don't see any current need for extra locking here.
Veil ensures that only one session ever calls LWLockAssign(), and as the
Veil LWLock is allocated on the first piece of user-invoked SQL to call
a Veil function, I see no scope for races between Veil and the rest of
Postgres.
Maybe
Neil, Jim, All:
> Personally, I think delivering all notifications by default is simpler
> behavior for the application programmer to understand. If you want to
> avoid doing work for duplicate notifications, you realistically need to
> implement that yourself anyway.
I agree with Neil; I don't r
Tom Lane said:
> But I think you might be confusing that with the feature-or-bug
> (depending on one's point of view) that duplicate notifications can be
> merged into one event. I'm inclined to preserve that behavior,
> primarily because not doing so would create a tremendous penalty on
> applica
Jaime Casanova <[EMAIL PROTECTED]> writes:
> On 10/8/05, Tom Lane <[EMAIL PROTECTED]> wrote:
>> This is exactly the same example discussed in previous threads on this
>> issue. Do you think it will change anyone's mind?
> in any case, i still think that is better to get bad performance
> because
Hi,
Which way do you suggest to "Prevent libpq's PQfnumber() from
lowercasing the column name" (which is listed as a TODO item). If
column name has quotes around it we're just removing the quotes and
comparing with the related column name. Else, lowercasing the column
name and then comparing.
I c
Am Samstag, den 08.10.2005, 18:03 -0400 schrieb Tom Lane:
> Josh Berkus writes:
> >> I was wonderring, because I create a lot of server side utility functions,
> >> whether adding an option to pg_dump to just dump functions has been
> >> considered. I did a quick perusal of the code, and noted tha
Well, _bt_compare is used for every btree index in the system,
including all the system indexes. A fresh initdb already has several
dozen indexes already so your code has to deal with that.
Remember, _bt_compare compares strings, integers, floats, dates, etc
and your code needs to work for all of
On Wed, 2005-09-28 at 14:26 -0400, Bruce Momjian wrote:
> I have added a section to the top of the WAL docs explaining caching and
> reliability issues:
>
> http://candle.pha.pa.us/main/writings/pgsql/sgml/reliability.html
>
> I also renamed the chapter "Reilability" rather than "WAL."
>
On 10/8/05, Tom Lane <[EMAIL PROTECTED]> wrote:
> Jaime Casanova <[EMAIL PROTECTED]> writes:
> > but this example seems to clarify (or at least i think) that we have to
> avoid
> > pulling up subquerys containing volatile functions:
>
> This is exactly the same example discussed in previous threads
10 matches
Mail list logo
