Well, I have searched a bit more about the zone_reclaim_mode thing, and
obviously I am not the first one having problems with it. It seems, there was
some kind of logic introduced to the kernel, which decided that our machine
must be a NUMA architecture (which it is not), and as a consequence,
"Craig Ringer" wrote in message
news:4c33dc32.7080...@postnewspapers.com.au...
> On 06/07/10 17:47, Davor J. wrote:
>> Thanks Craig.
>>
>> I still find it a bit awkward that we have to use "priv check function"-s
>> because we can't define triggers on or reference to system tables. I
>> think
>>
I am in the process of moving a FoxPro based system to PostgreSQL.
We have several tables that have memo fields which contain carriage
returns and line feeds that I need to preserve. I thought if I converted
these into the appropriate \r and \n codes that they would be imported as
carriage returns
Hi,
please delete the http://www.postgresql.org/ftp/binary/8.3.11/ folder,
it is redundant to the http://www.postgresql.org/ftp/binary/v8.3.11/ and
only contains solaris binaries. My coworker just didn't find out how to
download postgres.
regards,
Daniel Migowski
--
Sent via pgsql-general
On 14/07/2010 7:04 PM, t...@exquisiteimages.com wrote:
I am in the process of moving a FoxPro based system to PostgreSQL.
We have several tables that have memo fields which contain carriage
returns and line feeds that I need to preserve. I thought if I converted
these into the appropriate \r and
On Tue, Jul 13, 2010 at 02:53:25PM -0500, Anthony Presley wrote:
> I'm bordering on insanity, trying to track down an IDLE in transaction
> problem.
you might find this helpful:
http://www.depesz.com/index.php/2008/08/28/hunting-idle-in-transactions/
Pozdrawiam,
Hubert Lubaczewski
--
Linkedin:
hi,
On Wed, 2010-07-14 at 13:40 +0200, Daniel Migowski wrote:
>
> please delete the
> http://www.postgresql.org/ftp/binary/8.3.11/ folder,
> it is redundant to the
> http://www.postgresql.org/ftp/binary/v8.3.11/ and
> only contains solaris binaries.
Thanks for the heads-up. Fixed. Changes wil
Andras Fabian wrote:
Here is a lengthy discussion about the topic (so no need for me to start it
again at LKML - and obviously it is not Ubuntu specific :-)
http://lkml.org/lkml/2009/5/12/58
Once there's some sort of resolution there, you might want to create an
Ubuntu bug report anyw
Craig Ringer wrote:
>> I am in the process of moving a FoxPro based system to PostgreSQL.
>> We have several tables that have memo fields which contain carriage
>> returns and line feeds that I need to preserve. I thought if I converted
>> these into the appropriate \r and \n codes that they wou
Hi All
I am using a cluster setup with two nodes in it. Replication between two
nodes is being done through slony.
Postgres version is 8.1.2 and slony version is 1.1.5 .
On Master node an error "CDT FATAL: invalid frontend message type 69"
encountered at 10:51 and postgres crashed.
There w
Hi Scott
I looked into the release notes of 8.4.2 and found the following fix in
the fix list for 8.4.2 :
Ensure that a cursor's snapshot is not modified after it is created
(Alvaro)
This could lead to a cursor deliver
Hubert,
:-) Your script was one of the first that I found, thanks to the power
of Google.
My issue with your script is that, for one reason or another, when
piping the logs through rsyslog, we end up with log lines that your perl
code won't help, like:
Jul 12 04:02:10 artemis postgres[27803]: [
tamanna madaan wrote:
The same fix is not included in fix list for postgres-8.1.19 which came
at the same time when postgres-8.4.2 was released i.e 14th Dec.,2009.
Its not there in any of the 8.1 releases after that i.e 8.1.20 and 21.
See http://archives.postgresql.org/pgsql-committers/2009-
On Wed, Jul 14, 2010 at 08:48:20AM -0500, Anthony Presley wrote:
> IE, the duration ends up on a different line, and basically none of the
> statements ever match in your perl script.
> Any guess here?
You can modify the script to match format, but I have simpler solution -
don't use syslog - at l
Craig Ringer wrote:
> [...]
>>> I would like to get "unit", but I just get an empty array ({}).
>>> How can I get "unit" ?
>> AFAIK, this is not related to PostgreSQL, but inherent to
>> XPath in that it returns elements from the document that
>> fulfill the XPath expression *unchanged*.
> My (
Howdy,
I'm trying to think of the best way to handle this situation.
I've got 2 tables, X and Y
Table X has a field foo varchar(20)
Table Y has a field bar varchar(20)
I want to enforce, that if table X.foo = 'dave' then you can't insert (or
update) Y.bar = 'dave'
I know this is ideally done
On Wed, Jul 14, 2010 at 01:20:25PM +, Tim Landscheidt wrote:
> Craig Ringer wrote:
>
> >> I am in the process of moving a FoxPro based system to PostgreSQL.
>
> >> We have several tables that have memo fields which contain carriage
> >> returns and line feeds that I need to preserve. I thoug
Hi guy,
I just droped a development database by mistake using the dropdb command
witch contains valuable data.
Can I still restaure it ? I have no backup.
Best regards,
Romain
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://w
On Wed, Jul 14, 2010 at 08:47:35AM +0800, Craig Ringer wrote:
> On 13/07/2010 10:52 PM, Greg Smith wrote:
>
> >I heard a scholarly treatment of that topic from Jim Nasby recently,
> >where he proposed a boolean GUC to toggle the expanded search behavior
> >to be named plan_the_shit_out_of_it.
>
>
On Wed, 2010-07-14 at 18:18 +0200, easyCity Team wrote:
> Hi guy,
>
> I just droped a development database by mistake using the dropdb command
> witch contains valuable data.
>
> Can I still restaure it ? I have no backup.
No.
Sincerely,
Joshua D. Drake
--
PostgreSQL.org Major Contributor
C
On Tue, Jul 13, 2010 at 4:03 AM, ced45 wrote:
>
> Hi List,
>
> I have trouble using XPath name() function in a XML field.
> For example, when I execute the following query :
>
> SELECT XPATH('name(/*)', XMLPARSE(DOCUMENT 'value'))
>
> I would like to get "unit", but I just get an empty array ({}).
We are doing an upgrade soon, and are wondering if its worth waiting
till version 9.0 is put into production.
I found that its projected to be mid-August at the following wiki. I
wasn't sure if there might be some more recent up to date information.
http://wiki.postgresql.org/wiki/PostgreSQL
On Wed, 2010-07-14 at 13:05 -0400, Darin Del Vecchio wrote:
> We are doing an upgrade soon, and are wondering if its worth waiting
> till version 9.0 is put into production.
>
> I found that its projected to be mid-August at the following wiki. I
> wasn't sure if there might be some more recent
I'm having some difficulty getting plpgsql to recognize a function with
a couple of OUT parameters. I'm either declaring the function
incorrectly, making the call to it in the wrong way or my program is
simply possessed by evil spirits. I'm using Postgres 8.1.5.
What appears to be happening is
On 14 Jul 2010, at 18:13, David Kerr wrote:
> Howdy,
>
> I'm trying to think of the best way to handle this situation.
>
> I've got 2 tables, X and Y
>
> Table X has a field foo varchar(20)
> Table Y has a field bar varchar(20)
>
> I want to enforce, that if table X.foo = 'dave' then you can'
Hello
PostgreSQL use OUT params very untypically. You can't to directly to
join OUT parameter with some variable. It isn't possible.
please, try
CREATE OR REPLACE FUNCTION foo(a int, b int, OUT c int, OUT d int)
RETURNS record AS $$
BEGIN
c := a + 1;
d := b + 1;
RETURN;
END;
$$ LANGUAGE pl
On Wed, 2010-07-14 at 12:21 -0600, Bill Thoen wrote:
> I'm having some difficulty getting plpgsql to recognize a function with
> a couple of OUT parameters. I'm either declaring the function
> incorrectly, making the call to it in the wrong way or my program is
> simply possessed by evil spirits
David Fetter wrote:
> [...]
>> Another option is a small Perl script or something similar
>> that connects to both the FoxPro and the PostgreSQL database
>> and transfers the data with parameterized "INSERT". The ad-
>> vantage of this is that you have tight control of charsets,
>> date formats,
"Joshua D. Drake" writes:
> On Wed, 2010-07-14 at 12:21 -0600, Bill Thoen wrote:
>> I'm having some difficulty getting plpgsql to recognize a function with
>> a couple of OUT parameters.
>> psql:ex_out_fail.sql:28: ERROR: function fishy(text, text, integer,
>> real) does not exist
> You are p
Hi all,
We tend to do a lot of lookups on our database that look something like:
select
e.id
from
employee e ,app_user au
where
au.id=user_id and
au.corporation_id=$1 and
e.ssn is not null and
e.ssn!=' ' and
e.ssn!='' and
e.deleted='N'and
bytea2text(DECRYPT(decode(e.ssn,
Following on the smashing success of PostgreSQL Conference East,
PostgreSQL Conference West, The PostgreSQL Conference for Decision
Makers, End Users and Developers, is being held at the St. Francis,
Westin Hotel in San Francisco from November 2nd through 4th 2010. Please
join us in making this the
In response to Anthony Presley :
> Hi all,
>
> We tend to do a lot of lookups on our database that look something like:
>
> select
> e.id
> from
> employee e ,app_user au
> where
> au.id=user_id and
> au.corporation_id=$1 and
> e.ssn is not null and
> e.ssn!=' ' and
> e.ssn!=
On 14 July 2010 20:23, Anthony Presley wrote:
> Hi all,
>
> We tend to do a lot of lookups on our database that look something like:
>
> select
> e.id
> from
> employee e ,app_user au
> where
> au.id=user_id and
> au.corporation_id=$1 and
> e.ssn is not null and
> e.ssn!=' ' and
> e.
On 14 July 2010 20:32, Bill Moran wrote:
> In response to Anthony Presley :
>
>> Hi all,
>>
>> We tend to do a lot of lookups on our database that look something like:
>>
>> select
>> e.id
>> from
>> employee e ,app_user au
>> where
>> au.id=user_id and
>> au.corporation_id=$1 and
>> e
Thom Brown writes:
> On 14 July 2010 20:23, Anthony Presley wrote:
>> select
>>e.id
>> from
>> employee e ,app_user au
>>where
>> au.id=user_id and
>> au.corporation_id=$1 and
>> e.ssn is not null and
>> e.ssn!=' ' and
>> e.ssn!='' and
>> e.deleted='N'and
>> bytea2text(DECRYPT(dec
Thanks guys. I think I see now. I was thinking it was a more transparent
pass-by-value / pass-by-reference thing.
Anyway I solved my problem by going back into my comfort zone and
explicitly return a record and I'm not using OUT parameters. They're
aren't what I thought they were and I'm workin
On Wed, 2010-07-14 at 15:56 -0400, Tom Lane wrote:
> Thom Brown writes:
> > On 14 July 2010 20:23, Anthony Presley wrote:
> >> select
> >>e.id
> >> from
> >> employee e ,app_user au
> >>where
> >> au.id=user_id and
> >> au.corporation_id=$1 and
> >> e.ssn is not null and
> >> e.ss
On Wed, 2010-07-14 at 20:32 +0100, Thom Brown wrote:
> On 14 July 2010 20:23, Anthony Presley wrote:
> > Hi all,
> >
> > We tend to do a lot of lookups on our database that look something like:
> >
> > select
> >e.id
> > from
> > employee e ,app_user au
> >where
> > au.id=user_id a
Excerpts from Greg Smith's message of mié jul 14 09:52:46 -0400 2010:
> tamanna madaan wrote:
> > The same fix is not included in fix list for postgres-8.1.19 which came
> > at the same time when postgres-8.4.2 was released i.e 14th Dec.,2009.
> > Its not there in any of the 8.1 releases after that
In response to Anthony Presley :
> On Wed, 2010-07-14 at 15:56 -0400, Tom Lane wrote:
> > Thom Brown writes:
> > > On 14 July 2010 20:23, Anthony Presley wrote:
> > >> select
> > >>e.id
> > >> from
> > >> employee e ,app_user au
> > >>where
> > >> au.id=user_id and
> > >> au.corp
On Wed, Jul 14, 2010 at 2:14 AM, tamanna madaan
wrote:
> Hi Scott
>
> I looked into the release notes of 8.4.2 and found the following fix in
> the fix list for 8.4.2 :
Your first priority should be updating to the latest 8.1 version
available. While it may or may not have had release notes made
Thanks to all that replied,
I used Joe Conway's suggestion, using grep and an extracted list of tables,
functions and views form the DB. It worked very well.
I will attach the code I used to this thread once complete.
Again Thanks
Andrew Bartley
On 14 July 2010 00:43, Greg Smith wrote:
> An
Hi!, maybe is a silly question but...
Exists some syntax standard to escape especial characters on querys???
i mean, the notation E'\\ to escape especial characters only works
in postgres (8.3.11) or this works on oracle, ms sql server too???
regards, eddie.
--
Sent via pgsql-general mai
(Sorry for the use/abuse of the pgsql-general list, but I wanted to get
this in front of as many people as possible)
I am inaugurating a monthly San Diego PostgreSQL Users Group. Details on
the first meetup can be found here:
http://www.meetup.com/SD-PUG/calendar/14105562/
I know there are a l
Hi everyone,
Looks like I'm encountering some quirks with coalesce()...
> postgres=# select coalesce(null,0);
> coalesce
> --
> 0
> (1 row)
>
> postgres=# SELECT COALESCE(ROUND(EXTRACT(epoch FROM now()-query_start)),0)
> FROM pg_stat_activity WHERE current_query = ' in transac
On 15 July 2010 00:52, Richard Yen wrote:
> Hi everyone,
>
> Looks like I'm encountering some quirks with coalesce()...
>
>> postgres=# select coalesce(null,0);
>> coalesce
>> --
>> 0
>> (1 row)
>>
>> postgres=# SELECT COALESCE(ROUND(EXTRACT(epoch FROM now()-query_start)),0)
>> F
Ah, I see what you mean. If there's no rows to return, then there's no
coalesce-ing to do...
sorry for the spam.
--Richard
On Jul 14, 2010, at 5:12 PM, Thom Brown wrote:
> On 15 July 2010 00:52, Richard Yen wrote:
>> Hi everyone,
>>
>> Looks like I'm encountering some quirks with coalesce
On 15/07/10 00:34, David Fetter wrote:
>> => WITH aconstant(constval) AS (VALUES(1)) SELECT x.*, constval FROM
>> generate_series(1,10) AS x;
>> ERROR: column "constval" does not exist
>> LINE 1: ...TH aconstant(constval) AS (VALUES(1)) SELECT x.*, constval F...
>
> You missed the CROSS JOIN, wh
Hello
I've used oracle for 10years,but I've never seen such notations.
In fact the SQL retuns an error .
postgres=# select E'\\';
?column?
--
\
(1 row)
SQL> select E'\\' from dual;
select E'\\' from dual
*
ERROR at line 1:
ORA-00923: FROM keyword not found where expected
On 07/13/2010 10:44 PM, Thom Brown wrote:
On 13 July 2010 21:25, Magnus Hagander wrote:
On Tue, Jul 13, 2010 at 20:10, Thom Brown wrote:
On 13 July 2010 17:14, Duncavage, Daniel P. (JSC-OD211)
wrote:
We are implementing Nagios on Space Station and want to use PostgreSQL to
store the data o
On Tue, Jul 13, 2010 at 8:16 AM, Andras Fabian wrote:
> I think I have found the solution.
> - zone_reclaim_mode
> (yes, in the kernel stack there was always also a call to "zone_reclaim").
Thanks so much for this. I too just got bit by the zone_reclaim_mode
slowing my file transfers to a craw
Hi All
I am using a cluster setup with two nodes in it. Replication between two
nodes is being done through slony.
Postgres version is 8.1.2 and slony version is 1.1.5 .
On Master node an error "CDT FATAL: invalid frontend message type 69"
encountered at 10:51 and postgres crashed.
There we
52 matches
Mail list logo
