Hi,
I have a database with views that can take up to 2 hours to be
calculated.
During that time, it's not possible to run a function that inserts data
into the database, apparently because this function disactivates a
trigger while it runs, by deleting and creating the trigger again at the
end. (
El Lun 25 Jul 2005 23:29, Stephan Szabo escribió:
> >
> > Now to the constraint:
> >
> > I don't want the login and password columns to have nulls when the account
> > (row) is confirmed (confirmed column is set to true).
> >
> > I tried adding this CONSTRAINT to the table definition, but with no l
I have been using postgresql (7.2.1-5) for several
years. Supprisingly, I've just got a problem when
doing pg_dumpall.
The error is :
psql: ERROR: getTypeOutputInfo: Cache lookup of type
0 failed
This error also occurs when i enter to postgres using
this command:
psql template1
User which i us
Hi All,
I've been lurking at both the bizgres and postgres mailing lists in recent
months to get some ideas for building a new db server. I saw some threads on
the 7k$ server and it sounds like the Opteron, lots of ram and raid10 is the
way to go. (my budget is +/- £6000 (=$1))
But I'm keen
"Philippe Lang" <[EMAIL PROTECTED]> writes:
> I have a database with views that can take up to 2 hours to be
> calculated.
> During that time, it's not possible to run a function that inserts data
> into the database, apparently because this function disactivates a
> trigger while it runs, by dele
I am using an Access front end to a PG 8.0 backend
using linked tables.
When I use referential integrity it gives me the
error:
This operation is not supported within
transactions
This error occurs when referential integrity is
used for both Cascade and restrict Delete. It actually does the
Riyad Aufari <[EMAIL PROTECTED]> writes:
> I have been using postgresql (7.2.1-5) for several
> years. Supprisingly, I've just got a problem when
> doing pg_dumpall.
> The error is :
> psql: ERROR: getTypeOutputInfo: Cache lookup of type
> 0 failed
> This error also occurs when i enter to postgre
dear sir,
could u plz. tell me that can i
interface postgreSql as a backend with the front end Visual basic6.0?and give me
idea that how can i do that?
thanks & regards
sutha
"Sim Zacks" <[EMAIL PROTECTED]> writes:
> I am using an Access front end to a PG 8.0 backend using linked tables.
> When I use referential integrity it gives me the error:
> This operation is not supported within transactions
There is no such error message within Postgres itself, so I suppose
Acce
Hi all,
Jumping in directly to the subject, this is what I get:
explain SELECT bigint_col_1, bigint_col_2 FROM big_table WHERE
bigint_col_2 in (12132131, null, null, null,
null);
QUERY PLAN
---
Seq Scan
Sutha wrote:
> dear sir, could u plz. tell me that can i interface postgreSql as a
> backend with the front end Visual basic6.0?and give me idea that how
> can i do that?
http://www.postgresql.org/download/
There are various Windows-related drivers there including ODBC.
However, if you weren't
Sim Zacks wrote:
I am using an Access front end to a PG 8.0 backend using linked tables.
When I use referential integrity it gives me the error:
This operation is not supported within transactions
This error occurs when referential integrity is used for both Cascade and
restrict Delete. It actua
Hi,
I meant: in 7.4.X databases, is there a way of disabling a trigger without
deleting it? I guess the answer is no.
That's what my plpgsql insert function does, and because of this, if a view is
running at the same moment on the same tables (some views can take up to 2
hours to be calculated
On Mon, 2005-07-25 at 22:02, Tom Lane wrote:
> Scott Marlowe <[EMAIL PROTECTED]> writes:
> > On Mon, 2005-07-25 at 16:56, Martijn van Oosterhout wrote:
> >> pg_dump should be able to dump any older version. It's a bug otherwise.
>
> > But FYI that backwards compatibility was introduced around 7.3
Scott Marlowe <[EMAIL PROTECTED]> writes:
> On Mon, 2005-07-25 at 22:02, Tom Lane wrote:
>> pg_dump believes it can dump from any server back to 7.0; if it can't,
>> that's a bug, and details would be appreciated.
> I thought the backwards dumping compatibility thing was fairly new (i.e.
> it show
On Fri, 2005-07-22 at 15:56 +0100, Alex Stapleton wrote:
> On 21 Jul 2005, at 17:02, Scott Marlowe wrote:
>
> > On Thu, 2005-07-21 at 02:43, vinita bansal wrote:
> >
> >> Hi,
> >>
> >> My application is database intensive. I am using 4 processes since
> >> I have 4
> >> processeors on my box. Th
Hi all,
I have been quite satisfied with the level of support
from the PostgreSQL community, but this time I'm
getting nothing. So, is transaction timeout option
planned at all? What's the alternative solution to a
client that's hung in transaction?
thanks,
Eugene
_
On Tue, 2005-07-26 at 09:26, Tom Lane wrote:
> Scott Marlowe <[EMAIL PROTECTED]> writes:
> > On Mon, 2005-07-25 at 22:02, Tom Lane wrote:
> >> pg_dump believes it can dump from any server back to 7.0; if it can't,
> >> that's a bug, and details would be appreciated.
>
> > I thought the backwards d
On Tue, Jul 26, 2005 at 07:40:30AM -0700, Dr NoName wrote:
> So, is transaction timeout option planned at all?
> What's the alternative solution to a client that's hung in
> transaction?
Forcibly end it?
--
Alvaro Herrera ()
"I dream about dreams about dreams", sang the nightingale
under the p
On Jul 26, 2005, at 7:35 AM, Filip Wuytack wrote:
I've been lurking at both the bizgres and postgres mailing lists in
recent
months to get some ideas for building a new db server. I saw some
threads on
the 7k$ server and it sounds like the Opteron, lots of ram and
raid10 is the
way to go.
Yeah, that's what we have to resort to now, but that's
not a solution. Until we kill the client, the entire
database is locked (or, at least the tables that other
clients need to write to, which is effectively the
same thing). This is annoying enough during the week
but it's especially a problem on
On Tue, Jul 26, 2005 at 07:40:30AM -0700, Dr NoName wrote:
>
> I have been quite satisfied with the level of support
> from the PostgreSQL community, but this time I'm
> getting nothing.
There have been a couple of replies to your post, although perhaps
not what you were hoping for:
http://archi
Filip,
On 7/26/05 4:35 AM, "Filip Wuytack" <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> I've been lurking at both the bizgres and postgres mailing lists in recent
> months to get some ideas for building a new db server. I saw some threads on
> the 7k$ server and it sounds like the Opteron, lots of r
Am Dienstag, 26. Juli 2005 16:07 schrieb Philippe Lang:
> Hi,
>
> I meant: in 7.4.X databases, is there a way of disabling a trigger without
> deleting it? I guess the answer is no.
>
> That's what my plpgsql insert function does, and because of this, if a view
> is running at the same moment on th
On Tue, 2005-07-26 at 09:40, Dr NoName wrote:
> Hi all,
>
> I have been quite satisfied with the level of support
> from the PostgreSQL community, but this time I'm
> getting nothing. So, is transaction timeout option
> planned at all? What's the alternative solution to a
> client that's hung in t
Hi anybody,
i a running PostgreSQL on Win2k and use PostgreSQL in my application via
an ODBC bridge.
In my aplication i create a database with default (SQL-ASCII) encoding,
strings containing vovels can be saved, but not read correctly.
I have created a database with WIN1250, WIN and UNIC
On Tue, 2005-07-26 at 10:33, Dr NoName wrote:
> Yeah, that's what we have to resort to now, but that's
> not a solution. Until we kill the client, the entire
> database is locked (or, at least the tables that other
> clients need to write to, which is effectively the
> same thing). This is annoying
On Tue, Jul 26, 2005 at 08:33:19AM -0700, Dr NoName wrote:
> A single client should not be able to bring the entire
> database down. The DB should recognize that the client
> went down and roll back the transaction. That would be
> the ideal solution. Anything else we can do to remedy
> the situat
> What's the client doing that takes locks strong
> enough to "lock up
> the entire database"? Why does the client hang?
yeah, good question. I thought postgres uses
better-than-row-level locking? Could the total
deadlock be caused by a combination of an open
transaction and VACUUM FULL that run
Hi,
I have a problem in
that I need to drop non-existent tables in a DDL script. This is in order that
the script can re-build a database schema if the tables already exist. However,
in Postgres this is proving to be a problem because if the table does not exist
then the DDL execution will s
> OK, for the third or fourth time, what kind of locks
> is your application
> taking out that can lock the whole database?
I'd like to know that myself. How can a
select/inser/update lock an entire table or even
multiple tables?
> How, exactly, can PostgreSQL (or any other database)
> recognize
> On Tue, Jul 26, 2005 at 08:33:19AM -0700, Dr NoName
> wrote:
>
> > A single client should not be able to bring the
> entire
> > database down. The DB should recognize that the
> client
> > went down and roll back the transaction. That
> would be
> > the ideal solution. Anything else we can do to
> The common view on this kind of thing is that if
> your client is broken,
> you need to fix it.
The problem is, we can't fix the users, nor can we fix
other software that our client has to interact with.
There will always be occasional situations when a
client gets stuck.
> That said, I have se
On Tue, 2005-07-26 at 11:24, Dr NoName wrote:
> > The common view on this kind of thing is that if
> > your client is broken,
> > you need to fix it.
>
> The problem is, we can't fix the users, nor can we fix
> other software that our client has to interact with.
> There will always be occasional
TIP 2: Don't 'kill -9' the postmaster
Dr NoName wrote:
The common view on this kind of thing is that if
your client is broken,
you need to fix it.
The problem is, we can't fix the users, nor can we fix
other software that our client has to interact with.
There will always be occasional
Review
http://www.anandtech.com/storage/showdoc.aspx?i=2480
Slashdot
http://hardware.slashdot.org/article.pl?sid=05/07/26/1229211&tid=198
Might be useful for those of us working with "budget" systems. If anyone
does make a purchase, please post your investigations to the list - I
for one wou
I'm currently trying to install a set of Perl modules that interact with
a particular SQL schema (bioperl-db with BioSQL, if anyone is familiar
with them), and am running into a problem that appears to be emergent
with 8.0.3.
I myself am still very new to PostgreSQL, so I'm having trouble tell
> > > That said, I have seen some folks post about writing a
> perl or shell
> > > script that runs every x minutes looking for connections
> that have
> > > been idle for > a certain amount of time and kill the backend
> > > associated with it (sigterm, not -9...)
> >
> > what are the implic
> If you have second database in the cluster is it
> still operational when
> the main database locks up?
we don't have a DB cluster. It would be pretty useless
since postgresql doesn't support distributed
transactions.
> Also it seems that some diagnostics are needed in
> the client app to log
"Philippe Lang" <[EMAIL PROTECTED]> writes:
> I meant: in 7.4.X databases, is there a way of disabling a trigger without
> deleting it? I guess the answer is no.
Nothing officially supported, anyway. There's a pg_trigger.tgenabled
column but I'm not sure which operations pay attention to it.
>
On Tue, 2005-07-26 at 12:41, Magnus Hagander wrote:
> > > > That said, I have seen some folks post about writing a
> > perl or shell
> > > > script that runs every x minutes looking for connections
> > that have
> > > > been idle for > a certain amount of time and kill the backend
> > > > asso
> > > > > That said, I have seen some folks post about writing a
> > > perl or shell
> > > > > script that runs every x minutes looking for connections
> > > that have
> > > > > been idle for > a certain amount of time and kill the backend
> > > > > associated with it (sigterm, not -9...)
> > > >
On Tue, 2005-07-26 at 12:51, Dr NoName wrote:
> > If you have second database in the cluster is it
> > still operational when
> > the main database locks up?
>
> we don't have a DB cluster. It would be pretty useless
> since postgresql doesn't support distributed
> transactions.
You misunderstoo
Andrew Stewart <[EMAIL PROTECTED]> writes:
> I myself am still very new to PostgreSQL, so I'm having trouble telling
> if there is anything wrong with the postgres transaction that is being
> attempted by the bioperl-db maketest. The verbose error output is as
> follows...
> preparing SELECT
> You misunderstood his point. In PostgreSQL
> parlance, a "cluster" is a
> single postmaster running on a single machine, with
> 1 or more
> databases. So, what he wanted to know was, if your
> application is
> hitting a database called fred, and you have a spare
> database named
> wilma, would
wayne schlemitz wrote:
> How do I remove my self from this mail list I have
> tried
> in the past with no luck. Please sent specific
> instructions.
>
> Wayne
>From the web, you could try here:
http://www.postgresql.org/community/lists/subscribe
and click the "unsubscribe" action.
___
How do I remove my self from this mail list I have
tried
in the past with no luck. Please sent specific
instructions.
Wayne
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
Scott Marlowe <[EMAIL PROTECTED]> writes:
> On Tue, 2005-07-26 at 12:41, Magnus Hagander wrote:
>> The only *safe* way to do it ATM is to restart the database. SIGTERM may
>> leave orphaned locks or such things in the system.
> Really? I was under the impression that doing a "kill " on
> an idle
I have this index:
"directory_lower_username_seg_key" unique, btree (lower(username)
text_pattern_ops, seg)
... but my query refuses to use that index.
[local]:owl=>explain select * from directory where lower(username) =
'jks@selectacast.net';
QUERY PLAN
---
On Tue, 2005-07-26 at 12:35 +0100, Filip Wuytack wrote:
> I've been lurking at both the bizgres and postgres mailing lists in recent
> months to get some ideas for building a new db server. I saw some threads on
> the 7k$ server and it sounds like the Opteron, lots of ram and raid10 is the
> way to
Joseph Shraibman wrote:
I have this index:
"directory_lower_username_seg_key" unique, btree (lower(username)
text_pattern_ops, seg)
... but my query refuses to use that index.
[local]:owl=>explain select * from directory where lower(username) =
'jks@selectacast.net';
Hi again,
I still can't connect. I need someone to tell me what
I can try to discover what the problem is.
Again, here's the problem:
pgSQL 8.0.3 install on WinXP SP1.
The install works fine. The DB starts and works until
we restart the computer. When the machine reboots, we
can't connect to t
Hello everyone,I am searching for a way to have my postgresql 7.4.7 backend be triggered to let the front end know there has been a change to the database. If more then one person is connected to the database and person (x) makes a change, I want other clients to then be aware of that, and refresh
On Tue, 2005-07-26 at 16:25, Adam O'Toole wrote:
> Hello everyone,
> I am searching for a way to have my postgresql 7.4.7 backend be
> triggered to let the front end know there has been a change to the
> database. If more then one person is connected to the database and
> person (x) makes a change,
Read the Rules section of the manual and the section on Rules vs Triggers.
>From what I get triggers are necessary for column constraints. As far as
speed, it seems there are some differences between how fast rules/triggers
would do the same action, but that some complex analysis is involved to
de
# [EMAIL PROTECTED] / 2005-07-26 18:25:23 -0300:
> Hello everyone,I am
> searching for a way to have my postgresql 7.4.7 backend be triggered to let
> the front end know there has been a change to the database. If more then one
> person is connected to the database and person (x) makes a change,
Madison Kelly wrote:
Joseph Shraibman wrote:
What happens if you 'SET enable_seqscan TO OFF' and try the query
again? I've had a couple of instances where the planner just doesn't
like my index but once it is told to use it I get a nice performance boost.
It still does a seqscan.
-
On Tue, Jul 26, 2005 at 06:04:08PM +0200, Walsh, Richard (Richard) wrote:
> I have a problem in that I need to drop non-existent tables in a DDL
> script. This is in order that the script can re-build a database schema
> if the tables already exist. However, in Postgres this is proving to be
> a pr
On Tue, Jul 26, 2005 at 02:33:04PM -0400, Tom Lane wrote:
> Well, it ought to, but I for one don't consider that code path
> adequately tested --- and we have seen at least one report (from Rod
> Taylor if memory serves) suggesting that there are in fact bugs in it.
>
> We know that SIGTERM'ing al
Stephan Szabo wrote:
On Tue, 26 Jul 2005, Joseph Shraibman wrote:
I have this index:
"directory_lower_username_seg_key" unique, btree (lower(username)
text_pattern_ops, seg)
... but my query refuses to use that index.
text_pattern_ops is an opclass for doing LIKE queries using the index
On Tue, 26 Jul 2005, Joseph Shraibman wrote:
> I have this index:
>
> "directory_lower_username_seg_key" unique, btree (lower(username)
> text_pattern_ops, seg)
>
> ... but my query refuses to use that index.
text_pattern_ops is an opclass for doing LIKE queries using the index, I
don't believe i
On Tue, 26 Jul 2005, Joseph Shraibman wrote:
>
>
> Stephan Szabo wrote:
> > On Tue, 26 Jul 2005, Joseph Shraibman wrote:
> >
> >
> >>I have this index:
> >>
> >>"directory_lower_username_seg_key" unique, btree (lower(username)
> >>text_pattern_ops, seg)
> >>
> >>... but my query refuses to use tha
# [EMAIL PROTECTED] / 2005-07-26 17:53:35 -0400:
> Read the Rules section of the manual and the section on Rules vs Triggers.
>
> From what I get triggers are necessary for column constraints. As far as
> speed, it seems there are some differences between how fast rules/triggers
> would do the sam
Stephan Szabo wrote:
It is for the operators ~<~, ~<=~, ~=~, ~>=~, ~>~ (for like optimization).
The docs seem to say that it does a character by character comparison
rather than one using the collation thus being better for pattern
matching. I'd think letting it do <, <=, =, >=, > would have i
On Tue, 26 Jul 2005, Joseph Shraibman wrote:
> Stephan Szabo wrote:
>
> > It is for the operators ~<~, ~<=~, ~=~, ~>=~, ~>~ (for like optimization).
> > The docs seem to say that it does a character by character comparison
> > rather than one using the collation thus being better for pattern
> > m
So can anyone suggest a solution that does not involve
killing the client when it hangs?
thanks,
Eugene
--- Dr NoName <[EMAIL PROTECTED]> wrote:
> > You misunderstood his point. In PostgreSQL
> > parlance, a "cluster" is a
> > single postmaster running on a single machine,
> with
> > 1 or more
Dr NoName wrote:
What's the client doing that takes locks strong
enough to "lock up
the entire database"? Why does the client hang?
yeah, good question. I thought postgres uses
better-than-row-level locking? Could the total
deadlock be caused by a combination of an open
transaction and
67 matches
Mail list logo
