On 26 Oct 2001 at 00:05 (-0400), Tom Lane wrote:
| Brent Verner <[EMAIL PROTECTED]> writes:
| > I'm not sure this is correct. I've tried to /make/ a SIGALRM cause
| > connect to errno==EINTR, but I can't cause this condition.
|
| It wouldn't surprise me in the least if this behavior is
| platfor
>
>
>
>It wouldn't surprise me in the least if this behavior is
>platform-dependent. It may well be that David's kernel will allow
>connect() to be interrupted by SIGALRM while yours won't. (Which
>reminds me that neither of you specified what platforms you were
>testing on. For shame.) Or may
Many signals may be the cause of -EINTR. It depends on what the signal
is as to how it's normally handled. sigalarm is the most common due to
it being a timer event.
Generate a timer that expires as fast as possible (not too fast to
prevent code execution), and you should see things left and
Brent Verner <[EMAIL PROTECTED]> writes:
> I'm not sure this is correct. I've tried to /make/ a SIGALRM cause
> connect to errno==EINTR, but I can't cause this condition.
It wouldn't surprise me in the least if this behavior is
platform-dependent. It may well be that David's kernel will allow
c
On 25 Oct 2001 at 17:08 (-0400), David Ford wrote:
| I'm fresh in the code, but this has solved my issues with PQconnect*
| failing when interrupted by signals. Some of it is sloppy and not to my
| liking yet, but I'm still digging through to see if anything else needs
| touched. Comments app
Tom Lane wrote:
>
> Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Also, I'm now a little worried about whether concurrent index creations
> >> will actually work. Both CREATE INDEX operations will try to update
> >> the pg_class tuple to set relhasindex true.
>
> > Yes but t
* tweekie <[EMAIL PROTECTED]> wrote:
|
| I asked this question a while back but got no response - is there any way of
| creating a Java stored procedure in a postgres database ? I can see that
| there is a built-in PL/sql type of environment and a python one but it would
| be nice if I could m
* Bill Studenmund <[EMAIL PROTECTED]> wrote:
| I would like the answer to be no. I would like our users to be able to
| dump a pre-schema-release db, upgrade, and then restore into a
| schema-aware PostgreSQL. And have their restore work.
Important point. Also having a standard is fine, but by
Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Also, I'm now a little worried about whether concurrent index creations
>> will actually work. Both CREATE INDEX operations will try to update
>> the pg_class tuple to set relhasindex true.
> Yes but there's a big difference. It's at
Mikhail Terekhov <[EMAIL PROTECTED]> writes:
> In my application I use 'LOCK seq'. In 7.0.2 it worked fine but in
> 7.1.2 Postgres complains that 'seq is not a table'. Is this
> (disabling to lock a sequences) an intended change?
Hmm, it wasn't thought about too much, but why in the world would y
I'm fresh in the code, but this has solved my issues with PQconnect*
failing when interrupted by signals. Some of it is sloppy and not to my
liking yet, but I'm still digging through to see if anything else needs
touched. Comments appreciated.
Honestly, I'm a bit surprised that this issue ha
Hi,
In my application I use 'LOCK seq'. In 7.0.2 it worked fine but in
7.1.2 Postgres complains that 'seq is not a table'. Is this
(disabling to lock a sequences) an intended change?
Thanks
Mikhail
---(end of broadcast)---
TIP 5: Have you checked
I have updated the HISTORY file to be current as of today. Marc, it may
be nice to repackage beta1 with that one file changed, but my guess is
that we will have a beta2 soon enough.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 8
CVS tags have been conssitent since v7.1 ...
On Thu, 25 Oct 2001, Peter Eisentraut wrote:
> Marc G. Fournier writes:
>
> > ... is now packaged ... mirrors will pick it up soon, but if anyone wants
> > to do a quick check, its in /pub/beta ...
>
> What ever happened to 7.2beta1?
>
> Sorry, but
On Thu, 25 Oct 2001, Peter Eisentraut wrote:
> Bill Studenmund writes:
>
> > Mainly because when we introduce schemas, all SQL transactions will have
> > to be performed in the context of *some* schema. I think "DEFAULT" was the
> > name you mentioned for when there was no schema matching the us
Bill Studenmund writes:
> > Because SQL says so. All objects in a schema belong to the owner of the
> > schema. In simple setups you have one schema per user with identical
> > names. This has well-established use patterns in other SQL RDBMS.
>
> Then implimenting schemas will cause a backward
Marc G. Fournier writes:
> ... is now packaged ... mirrors will pick it up soon, but if anyone wants
> to do a quick check, its in /pub/beta ...
What ever happened to 7.2beta1?
Sorry, but the inconsistency in naming of releases and CVS tags (if ever
there would be any) is driving me nuts.
--
Hello all
I asked this question a while back but got no response - is there any way of
creating a Java stored procedure in a postgres database ? I can see that
there is a built-in PL/sql type of environment and a python one but it would
be nice if I could migrate Java stored procedures in an
... is now packaged ... mirrors will pick it up soon, but if anyone wants
to do a quick check, its in /pub/beta ...
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
On Wed, 24 Oct 2001, Tom Lane wrote:
> Bill Studenmund <[EMAIL PROTECTED]> writes:
> > [ revised proposal for CREATE OPERATOR CLASS syntax ]
>
> I don't like the idea of writing a bunch of consecutive commas (and
> having to count them correctly) for cases where we're inserting
> noncontigous amo
> On Thu, 25 Oct 2001, Tom Lane wrote:
>
> > "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > > If we aren'g putting that Packaging stuff into v7.2, can we get it into
> > > beta as contrib also? Before I do the first packagingof the beta?
> >
> > Uh ... what?
> >
> > I just meant to wait a li
> On Thu, 25 Oct 2001, Tom Lane wrote:
>
> > "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > > If we aren'g putting that Packaging stuff into v7.2, can we get it into
> > > beta as contrib also? Before I do the first packagingof the beta?
> >
> > Uh ... what?
> >
> > I just meant to wait a li
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> If we aren'g putting that Packaging stuff into v7.2, can we get it into
> beta as contrib also? Before I do the first packagingof the beta?
Uh ... what?
I just meant to wait a little bit on wrapping the tarball while I make
this last(?) catalog u
On Thu, 25 Oct 2001, Teodor Sigaev wrote:
> Make me right if I mistake.
>
> When we was developing operator @@, I saw that postgres don't use index in
> select if operation has not commutator. But operator with different types in
> argument can't be commutator with itself. So I maked operator ~~
On Thu, 25 Oct 2001, Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > If we aren'g putting that Packaging stuff into v7.2, can we get it into
> > beta as contrib also? Before I do the first packagingof the beta?
>
> Uh ... what?
>
> I just meant to wait a little bit on wrappi
Philip Warner <[EMAIL PROTECTED]> writes:
> The problem in in the code to re-enable triggers:
> ...reltriggers = (select Count(*)
> So perhaps this version now has Count returning a bigint rather than an int?
Okay, I've added conversion functions for int8-to-int2 and vice versa.
Tom Lane writes:
> "Zeugswetter Andreas SB SD" <[EMAIL PROTECTED]> writes:
> > Imho one of the biggest sources for problems is people creating new
> > indexes on populated tables when the rest of the db/table has badly
> > outdated statistics or even only default statistics in place.
> > In this s
> my database server has very high load in this morning.
> I've found the problem. One of my index was not used so far!
> it's interesting:
> ...
> addb=> CREATE INDEX banners_b_no_key ON banners (b_no);
> CREATE
> addb=> EXPLAIN SELECT b_link FROM banners WHERE b_no = 3;
> NOTICE: QUERY PLAN:
>
Tom Lane wrote:
>
> Hannu Krosing <[EMAIL PROTECTED]> writes:
> > Is there a way to automatically ROLLBACK transactions that are
> > in "idle in transaction" for too long ?
>
> Nope, we don't have anything for that. Not clear to me that it's
> appropriate as a server-side function anyway.
This
D'oh ...
Okay, will hold off on packaging, but have already tag'd it ...
If we aren'g putting that Packaging stuff into v7.2, can we get it into
beta as contrib also? Before I do the first packagingof the beta?
On Thu, 25 Oct 2001, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
"Zeugswetter Andreas SB SD" <[EMAIL PROTECTED]> writes:
> Imho one of the biggest sources for problems is people creating new
> indexes on populated tables when the rest of the db/table has badly
> outdated statistics or even only default statistics in place.
> In this situation the optimizer is b
> Hello!
> It needs some help by the command
> VACUUM [VERBOSE] ANALYZE table;
> to choose the ideal query strategy.
How can I choose better query strategy than ...WHERE key_field = x; ?
Regards, Gabor.
---(end of broadcast)---
TIP 5: Have you c
Hello Tom!
Tom Lane wrote:
>
> Reiner Dassing <[EMAIL PROTECTED]> writes:
> > explain select * from wetter order by epoche desc;
> > NOTICE: QUERY PLAN:
>
> > Index Scan Backward using wetter_epoche_idx on wetter
> > (cost=0.00..3216018.59 rows=2034 width=16)
>
> > explain select * from w
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I have run pgindent on the C files and run pgjindent on the jdbc files
> as requested by the jdbc list. You can package up beta now. I will
> update the HISTORY file tomorrow with recent changes.
Please hold on that packaging until I add the int2<->in
i was wondering if the jan's work on SPI portal creation of prepared/saved
plans has something to do with caching query plan ?
thx in advance.
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Antonio Fiol =?iso-8859-1?Q?Bonn=EDn?= <[EMAIL PROTECTED]> writes:
> I say kind of, as I am not sure about it, or whether there is a newer
> version that does not show up the bug. Here's the description:
Please update to 7.1.3 and let us know whether you still see the
problem. We fixed a number
Hannu Krosing <[EMAIL PROTECTED]> writes:
> Is there a way to automatically ROLLBACK transactions that are
> in "idle in transaction" for too long ?
Nope, we don't have anything for that. Not clear to me that it's
appropriate as a server-side function anyway.
regards, t
Hello,
I've tried to search some postgresql mailing lists and i haven't found
an answer to my problem...
I create a function with the setof keyword...
create function employee(int) returns setof employee as 'select * from
employee where $1 = id'
language 'sql';
Instead of returning a tuple,
Hi All,
my database server has very high load in this morning.
I've found the problem. One of my index was not used so far!
it's interesting:
addb=> \d banners
Table "banners"
Attribute | Type | Modifier
> Of course the question "did you vacuum" (better, did you analyze) is
> annoying, just as the requirement to analyze is annoying in the first
> place, but unless someone designs a better query planner it
> will have to do. The reason why we always ask that question first is
> that people inva
Hi!
I say kind of, as I am not sure about it, or whether there is a newer
version that does not show up the bug. Here's the description:
When I use the following request (either on psql or using JDBC), the
backend crashes, making the other backends fail spectacularly.
The beast:
select S.last
>
>I'll take a shot at improving the documentation for bytea. I'm hoping
>documentation patches are accepted during beta though ;-)
>
>Also, FWIW, 7.2 includes bytea support for LIKE, NOT LIKE, LIKE ESCAPE,
>||, trim(), substring(), position(), length(), indexing, and various
>comparators.
>
C
Hello,
This is my first post here.
I've tried to search the archive and i haven't found
an answer to my problem...here it is...
I created a function with the "create function+setof" keywords...
create function employee(int) returns setof employee as 'select * from
employee where $1 = id'
langu
>>Wait a second, how can you do that? Doesn't that violate
>>pg_amop_opc_strategy_index ?
>>
>
> It sure does, but running the script shows that the second insert
> doesn't try to insert any rows. There's no entry in the temp table
> for ~~ because its left and right operands are not the types t
Is there a way to automatically ROLLBACK transactions that are
in "idle in transaction" for too long ?
I remember it has been discussed on this list, but what is the current
status ?
This is a problem that has haunted me on several web applicatons using
application servers that have persisten
45 matches
Mail list logo
