On Aug 6, 2009, at 2:00 PM, Bill Moran wrote:
In response to Tom Lane :
decibel writes:
We recently had a problem with a database where the /var filesystem
got corrupted. This appears to have seriously impacted the
ability of
STDERR from Postgres to get put out to disk, which ended up bloc
Alban Hertroys wrote:
On 31 Jul 2009, at 3:25, Christine Desmuke wrote:
Samples from the regression.diffs:
*** ./expected/boolean.out Fri Jun 1 18:40:19 2007
--- ./results/boolean.out Thu Jul 30 19:16:33 2009
***
*** 75,83
(1 row)
SELECT ' tru e '::text::boolea
Hi Craig, the instructions are great. I've gone through them and confirmed
I'm getting the full details in the stack traces. When it happens again,
I'll post the most useful stack traces and we'll be able to look at it
properly. Thanks again for your help so far, the responsiveness is terrific.
-B
On Thu, 6 Aug 2009 16:58:02 -0400
Michael Glaesemann wrote:
> That's not a SELECT query per se: AIUI it's how the evaluation of
> the NEW != OLD expression is evaluated within the PL/pgSQL function
> as part of the IF statement (note the "line 2 at IF" context line).
> It's just saying the <> ope
On Thu, 6 Aug 2009, Paul Rogers wrote:
> Why does the attached script fail with a foreign key constraint violation?
Referential actions are not deferred when a constraint is marked
deferrable (as that appears to be what the spec wants), so ON DELETE
RESTRICT will still fail on the statement, whil
Paul Rogers writes:
> Why does the attached script fail with a foreign key constraint violation?
The ON DELETE RESTRICT is why. Per the fine manual:
[RESTRICT] is the same as NO ACTION except that the check is not
deferrable.
It's a bit odd, but that's the best interpretation w
On Thu, Aug 6, 2009 at 3:31 PM, Josh Trutwin wrote:
> On Thu, 6 Aug 2009 13:15:57 -0400
> Merlin Moncure wrote:
>
>> CREATE OR REPLACE FUNCTION set_last_modified ()
>> RETURNS TRIGGER
>> AS $$
>> BEGIN
>> IF NEW != OLD THEN -- 8.4 syntax
>> NEW.last_modified = NOW();
>> END IF;
>>
>> RE
Why does the attached script fail with a foreign key constraint violation?
Privileged/Confidential Information may be contained in this message.
If you are not the addressee indicated in this message (or responsible for
delivery of the message to such person), you may not copy or deliver this
On Aug 6, 2009, at 15:31 , Josh Trutwin wrote:
Interestingly, this syntax is accepted in 8.3.7, but SELECT queries
fail:
CREATE TRIGGER trigger_test_upd_set_last_mod
BEFORE UPDATE ON test_upd
FOR EACH ROW EXECUTE PROCEDURE set_last_modified();
Then:
UPDATE test_upd SET foo = 'foo' WHERE id =
On Thu, 6 Aug 2009 13:15:57 -0400
Merlin Moncure wrote:
> CREATE OR REPLACE FUNCTION set_last_modified ()
> RETURNS TRIGGER
> AS $$
> BEGIN
> IF NEW != OLD THEN -- 8.4 syntax
> NEW.last_modified = NOW();
> END IF;
>
> RETURN NEW;
> END;
> $$ LANGUAGE PLPGSQL;
Interestingly, this synt
On Thu, 6 Aug 2009 13:15:57 -0400
Merlin Moncure wrote:
> CREATE OR REPLACE FUNCTION set_last_modified ()
> RETURNS TRIGGER
> AS $$
> BEGIN
> IF NEW != OLD THEN -- 8.4 syntax
> NEW.last_modified = NOW();
> END IF;
>
> RETURN NEW;
> END;
> $$ LANGUAGE PLPGSQL;
Thanks - I'll try this.
In response to Tom Lane :
> decibel writes:
> > We recently had a problem with a database where the /var filesystem
> > got corrupted. This appears to have seriously impacted the ability of
> > STDERR from Postgres to get put out to disk, which ended up blocking
> > backends.
>
> > Because
Thanks that did it!
On Aug 6, 11:33 am, pavel.steh...@gmail.com (Pavel Stehule) wrote:
> Hello
>
> SELECT ... FROM
> (SELECT ... FROM A
> UNION ALL
> SELECT FROM B) s1
> JOIN C IN C.z = s1.z;
>
> Regards
> Pavel Stehule
>
> 2009/8/6 david.schruth :
>
>
>
> > I just realized what I posted
2009/8/6 David Fetter :
> On Thu, Aug 06, 2009 at 08:33:57PM +0200, Pavel Stehule wrote:
>> Hello
>>
>> SELECT ... FROM
>> (SELECT ... FROM A
>> UNION ALL
>> SELECT FROM B) s1
>> JOIN C IN C.z = s1.z;
>
> That last line should read:
>
> JOIN C ON C.z = s1.z;
I am sorry
Pavel
>
> Cheer
On Thu, Aug 06, 2009 at 08:33:57PM +0200, Pavel Stehule wrote:
> Hello
>
> SELECT ... FROM
> (SELECT ... FROM A
>UNION ALL
>SELECT FROM B) s1
> JOIN C IN C.z = s1.z;
That last line should read:
JOIN C ON C.z = s1.z;
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 41
decibel writes:
> We recently had a problem with a database where the /var filesystem
> got corrupted. This appears to have seriously impacted the ability of
> STDERR from Postgres to get put out to disk, which ended up blocking
> backends.
> Because of this we want to switch from using STD
On Thu, Aug 6, 2009 at 1:38 PM, Jeff Davis wrote:
> On Thu, 2009-08-06 at 13:15 -0400, Merlin Moncure wrote:
>> in 8.4 you can (and should) do:
>> WHERE old = new
>
> I couldn't get that to work in a rule.
it should, maybe try old::foo = new::foo
>> IF NEW != OLD THEN -- 8.4 syntax
>
> Does th
Hello
SELECT ... FROM
(SELECT ... FROM A
UNION ALL
SELECT FROM B) s1
JOIN C IN C.z = s1.z;
Regards
Pavel Stehule
2009/8/6 david.schruth :
> I just realized what I posted was perfectly valid SQL. The following
> is more what I had in mind:
>
> (SELECT x,y,z FROM A
> UNION
> SELECT x,y,z
2009/8/6 Jeff Davis :
> On Thu, 2009-08-06 at 13:15 -0400, Merlin Moncure wrote:
>> in 8.4 you can (and should) do:
>> WHERE old = new
>
> I couldn't get that to work in a rule.
>
>> IF NEW != OLD THEN -- 8.4 syntax
>
> Does this work correctly in the case of NULLs? It looks like it does,
> but
I just realized what I posted was perfectly valid SQL. The following
is more what I had in mind:
(SELECT x,y,z FROM A
UNION
SELECT x,y,z FROM B)
AB JOIN C ON C.z = AB.z
This version certainly does throw an error.
Basically I'm wondering if there is a way to get Postgres to treat the
result of a
Simple question:
Is there a way to do something like the following:
SELECT x,y,z FROM A
UNION
SELECT x,y,z FROM B
JOIN C ON C.z = B.z
Thanks,
Dave
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgs
On Thu, 2009-08-06 at 13:15 -0400, Merlin Moncure wrote:
> in 8.4 you can (and should) do:
> WHERE old = new
I couldn't get that to work in a rule.
> IF NEW != OLD THEN -- 8.4 syntax
Does this work correctly in the case of NULLs? It looks like it does,
but that seems strange, because ROW(1, N
On Jul 26, 2009, at 1:32 PM, Ivan Sergio Borgonovo wrote:
Actually a serializable transaction doesn't even seem a too bad
solution... but I just would like to understand better how to manage
this situation so that I could make it as simple as possible AND
lower as much as possible the chances tha
On Thu, 2009-08-06 at 11:53 -0500, Josh Trutwin wrote:
> The set_last_modified() trigger is run even though the data didn't
> actually change. Perhaps due to an application program which doesn't
> know the contents before running the UPDATE.
The following doc explains the standard way to accompli
On Thu, Aug 6, 2009 at 12:53 PM, Josh Trutwin wrote:
> Hello,
>
> I have a simple table that has a trigger to set a last_modified column
> using the following:
>
> CREATE OR REPLACE FUNCTION set_last_modified ()
> RETURNS TRIGGER
> AS $$
> BEGIN
> NEW.last_modified = NOW();
> RETURN NEW
On Thu, Aug 06, 2009 at 07:23:41AM -0700, Nicolas wrote:
> Now, I'm in a situation where I have many "IDLE in transaction". I
> spotted them myself. I could kill them, but that wouldn't prevent them
> from happening again. In fact, it happens regularily.
>
> Is there a way to get the list of SQL s
Hello,
I have a simple table that has a trigger to set a last_modified column
using the following:
CREATE OR REPLACE FUNCTION set_last_modified ()
RETURNS TRIGGER
AS $$
BEGIN
NEW.last_modified = NOW();
RETURN NEW;
END;
$$ LANGUAGE PLPGSQL;
CREATE TRIGGER trigger_test_upd_set_la
We recently had a problem with a database where the /var filesystem
got corrupted. This appears to have seriously impacted the ability of
STDERR from Postgres to get put out to disk, which ended up blocking
backends.
Because of this we want to switch from using STDERR to using syslog,
but
On 27 juil, 21:49, t...@sss.pgh.pa.us (Tom Lane) wrote:
> Robert James writes:
> > Hi. I noticed that when clients (both psql and pgAdmin) disconnect or
> > cancel, queries are often still running on the server. A few questions:
> > 1) Is there a way to reconnect and get the results?
>
> No.
>
>
On 06/08/2009 13:42, sub_woofer wrote:
> Hello all
>
> To backup my postgresql data I use the pg_dumpall command which dumps all my
> databases to a .sql file.
>
> If I would like to restore a single database from this file how would I do
> this? Is it possible using PgAdmin - as this only allows
Hello all
To backup my postgresql data I use the pg_dumpall command which dumps all my
databases to a .sql file.
If I would like to restore a single database from this file how would I do
this? Is it possible using PgAdmin - as this only allows us to restore a
database from a .backup file???
Wh
sw...@opspl.com wrote:
>
>
> >
> > Seems unlikely (IOW, if so, you've found a bug no one else has ever
> > seen). Maybe they are being created implicitly by SERIAL column
> > declarations?
> >
>
> Yeah they are created by the Serial column .
He means: are they output as SERIAL columns i
On 5 Aug 2009, at 19:27, Scott Marlowe wrote:
On Wed, Aug 5, 2009 at 6:56 AM, Csaba Nagy wrote:
Hi Andor,
On Wed, 2009-08-05 at 14:15 +0200, Schindler Andor wrote:
Can anyone tell me, how this is possible? If we insert 12 on the
end, then
it decreases, but 11 remains the same. The problem on
On Thu, Aug 6, 2009 at 12:00, Abraham, Danny wrote:
> The server intermittently fails on simple queries.
> Log full of the above error log.
>
> Does anyone know on which version this problem is fixed?
> Or a specific patch?
Please see
http://blog.hagander.net/archives/149-Help-us-test-a-patch-for
On 31 Jul 2009, at 3:25, Christine Desmuke wrote:
Samples from the regression.diffs:
*** ./expected/boolean.out Fri Jun 1 18:40:19 2007
--- ./results/boolean.out Thu Jul 30 19:16:33 2009
***
*** 75,83
(1 row)
SELECT ' tru e '::text::boolean AS invalid;-- err
I don't believe it's been fixed. It seems like the folks who hack the
windows port haven't got a reproduceable failure.
On Thu, Aug 6, 2009 at 4:00 AM, Abraham, Danny wrote:
> The server intermittently fails on simple queries.
> Log full of the above error log.
>
> Does anyone know on which versi
On 5 Aug 2009, at 3:41, Richard Esmonde wrote:
Currently, the end of my pg_hba.conf file looks like:
host all all 10.5.5.0 255.255.255.0 ldap "ldap://
master1. belfry.lan:389/ou=Belfry
Users,ou=programmers;dc=belfry,dc=lan;cn=*;
On 4 Aug 2009, at 13:09, Der Tung wrote:
But know I have two Users A and B in different timezones.
When A saves a timestamp I want B to:
- Get the timestamp displayed in his timezone
- Get the timestamp displayed in the timezone a originally
saved it in
Does the type “time
Adding memory and releasing several memory consumers did the trick.
Thanks a lot.
Danny Abraham
BMC Software
CTM&D Business Unit
972-52-4286-513
danny_abra...@bmc.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgres
Hi!
Thanks...
Sorry, but this is not good solution for me, because of the webserver is
not opened (port) to the net, and I must compare local, a web dbs.
So I try to find a solution, that can create a "map" from structure in
XML, text, etc., and I can get it with ftp and compare it...
First I
The server intermittently fails on simple queries.
Log full of the above error log.
Does anyone know on which version this problem is fixed?
Or a specific patch?
Thanks
Danny Abraham
BMC Software
CTM&D Business Unit
972-52-4286-513
danny_abra...@bmc.com
--
Sent via pgsql-general mailing lis
Hi,
I can't find any more the place from where I downloaded acl_admin.
There is a very small problem with chown_all
Since a sequence may be owned by a table... and the function may try
to change the ownership of the seq first the function may abort
earlier.
A quick hack that may works in most si
Eugen Dueck wrote:
Now I was hoping for a feature that goes even further than the ones discussed
and allows clients to listen on changes in the database that satisfy real
WHERE clauses, if used on tables, but I could imagine that you can listen for
all changes caused by any DDL or DML stateme
Richard Esmonde wrote:
I'm new to PostGres (so go easy on my naivety). I am trying to configure
the postgres host based configuration file to permit users to authenticate
against our Active Directory.
OK. Never tried that myself, but let's see.
Needless to say both Ubuntu server and AD are i
On Wed, Aug 5, 2009 at 18:47, Michael
Gould wrote:
>
> I am wondering how others handle the login situation. We use Active
> Directory and require our users to change their passwords every 30 days.
> Currently in our old system using SQL Anywhere we use the integrated login
> feature. Our db serv
45 matches
Mail list logo