http://pqxx.org/development/libpqxx/
I'm in the process of creating a macport for libpqxx. I could use
some help from anyone with experience in building postgresql or
libpqxx on OSX, esp. against the macport libraries.
Thanks, Darren
--
Sent via pgsql-general mailing list (pgsql-general@postgr
"Leif B. Kristensen" wrote:
>I don't know how this is handled in Windows, but on a Linux computer you
>can enter the directory /usr/local/share/locale/de/LC_MESSAGES/ and
>just rename or delete the file psql.mo.
Thanks for the tipp: After renaming folder
C:\Program Files\PostgreSQL\8.3\share\lo
YES! Done - my listen addresses was the default.
Thanks Richard!
Nina
-Original Message-
From: Richard Huxton [mailto:[EMAIL PROTECTED]
Sent: September 19, 2008 11:57
To: Markova, Nina
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] setting Postgres client
Markova, Nina wrote:
On Friday 19. September 2008, Rainer Bauer wrote:
>I installed 8.3.3 on an english WinXP. The database cluster was
> initialized with server encoding UTF8 and the locale was set to
> 'German, Germany'.
>
>Now all messages in the log and everywhere else are showing up in
> German (as expected). How
--- On Fri, 9/19/08, Yi Zhao <[EMAIL PROTECTED]> wrote:
> From: Yi Zhao <[EMAIL PROTECTED]>
> Subject: [GENERAL] how to return the first record from the sorted records
> which may have duplicated value.
> To: "pgsql-general"
> Date: Friday, September 19, 2008, 8:51 AM
> hi all:
> I have a tab
Markova, Nina wrote:
>
> Thanks Richard.
>
>
> I specified the host IP ( I use the default 5432 port), got error:
> psql: could not connect to server: Connection refused
> Is the server running on host "192.168.XX.XXX" and accepting
> TCP/IP connections on port 5432?
>
> The on
Markova, Nina wrote:
Thanks Richard.
I specified the host IP ( I use the default 5432 port), got error:
psql: could not connect to server: Connection refused
Is the server running on host "192.168.XX.XXX" and accepting
TCP/IP connections on port 5432?
The only tcp lines in my
"Robert Haas" <[EMAIL PROTECTED]> writes:
> That doesn't seem to work, because IS NOT DISTINCT FROM is not an
> operator.
Yah :-(
> So then I tried creating an operator === (anyelement,
> anyelement) that just does IS NOT DISTINCT FROM and writing:
> select 1 === any(array[1]);
> which got me:
>
Thanks Richard.
I specified the host IP ( I use the default 5432 port), got error:
psql: could not connect to server: Connection refused
Is the server running on host "192.168.XX.XXX" and accepting
TCP/IP connections on port 5432?
The only tcp lines in my postgres.conf are
#tc
"Markova, Nina" <[EMAIL PROTECTED]> wrote:
>
> - On the client I tried:
> psql sta
> psql: could not connect to server: No such file or directory
> Is the server running locally and accepting
> connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
The client tries to connect to
On Fri, Sep 19, 2008 at 4:17 AM, Andrea Moretto
<[EMAIL PROTECTED]> wrote:
> Hi there,
>
> I am currently running Postgres 8.3.1.
>
> I've got a table called DETAILS, the primary key is : DE_ID char(12), there
> is another field CO_ID char (12).
> DE_ID and CO_ID are indexed with a btree. This tab
I'm trying to write a SQL statement to determine whether a value is an
an array, but I want the comparison to be done using IS NOT DISTINCT
FROM rather than =.
My first thought was that instead of writing:
SELECT value = ANY(array)
...I could simply write:
SELECT value IS NOT DISTINCT FROM ANY(
My message didn't get through the 1st time.
-Original Message-
From: Markova, Nina
Sent: September 17, 2008 17:33
To: pgsql-general@postgresql.org
Subject: Help on setting Postgres client
I have setup a Postgres server (8.2.4) on Solaris 10, for now in the
global zone, with FS :
/pg
As Richard already pointed out the query issues, I'll point out the
low-hanging fruit.
At 6:17am -0400 on Fri, 19 Sep 2008, Andrea Moretto wrote:
> I am currently running Postgres 8.3.1.
^
The current minor release is 8.3.3 and 8.3.4 is expected Monday.
U
> From: Bill Moran <[EMAIL PROTECTED]>
>
> Maybe that's not _always_ the right answer, but it
> seems to be a good
> answer 99% of the time. Sounds like your developers are
> using the
> database for what it was intended for, instead of just
> doing single
> row selects like a lot of amateurs I
Glyn Astill <[EMAIL PROTECTED]> wrote:
>
> > From: Harald Armin Massa <[EMAIL PROTECTED]>
> > Hello Glyn,
> >
> > Our legacy apps have some permanent tables that they use
> > for tempory data
> > > and constantly clear out, I've kicked the
> > developers and I intend to
> > > eradicate them eventu
Hi all,
I installed 8.3.3 on an english WinXP. The database cluster was initialized
with server encoding UTF8 and the locale was set to 'German, Germany'.
Now all messages in the log and everywhere else are showing up in German (as
expected). However I want to see those messages in English. I tri
> From: Harald Armin Massa <[EMAIL PROTECTED]>
> Hello Glyn,
>
> Our legacy apps have some permanent tables that they use
> for tempory data
> > and constantly clear out, I've kicked the
> developers and I intend to
> > eradicate them eventually (the tables, not the
> developers).
> >
>
> and wha
Hello Glyn,
Our legacy apps have some permanent tables that they use for tempory data
> and constantly clear out, I've kicked the developers and I intend to
> eradicate them eventually (the tables, not the developers).
>
and what is the problem with this usage? That is a perfectly valid thing to
> From: Richard Huxton <[EMAIL PROTECTED]>
> > The only way I can think so far is to do a select
> SESSION_USER in the
> > trigger function and skip the action if it matched my
> user.
>
> That's exactly it. I'm not sure it will ever be a
> built-in feature,
> everyone's requirements will be slig
Hi chaps,
Our legacy apps have some permanent tables that they use for tempory data and
constantly clear out, I've kicked the developers and I intend to eradicate them
eventually (the tables, not the developers).
These tables are constantly being autovacuumed, approximately once a minute,
it's
Dear Richard,
you are right. So Postgres takes a lot of time to get out an
impossible result!
The query I wrote is just a test, the concatenation is only a dummy.
On 19/set/08, at 12:33, Richard Huxton wrote:
Andrea Moretto wrote:
I've got a table called DETAILS, the primary key is : DE_
Glyn Astill wrote:
> I've a trigger written in C and I want to stop it fireing for a
> specific user. Is ther any way to do this outside of the C code in
> the trigger function?
>
> The only way I can think so far is to do a select SESSION_USER in the
> trigger function and skip the action if it m
Andrea Moretto wrote:
> I've got a table called DETAILS, the primary key is : DE_ID char(12),
> there is another field CO_ID char (12).
> If I run "explain analyze select * from details where co_id || co_id =
> '0100760153722324445';" it runs a sequential scan not using the index
> (which takes ab
Hi there,
I am currently running Postgres 8.3.1.
I've got a table called DETAILS, the primary key is : DE_ID char(12),
there is another field CO_ID char (12).
DE_ID and CO_ID are indexed with a btree. This table is about 140
millions of records.
If I execute an "explain select * from det
hello
2008/9/19 Michael Toews <[EMAIL PROTECTED]>:
> The INSERT and DELETE TG_OPs are straightforward (the simplest solution
> for these is that the existence of the primary key can be checked in the
> other table), however the UPDATE handler is really confusing.
>
> Is it possible for a trigger f
I've a trigger written in C and I want to stop it fireing for a specific user.
Is ther any way to do this outside of the C code in the trigger function?
The only way I can think so far is to do a select SESSION_USER in the trigger
function and skip the action if it matched my user.
--
Sent
now, I do it like this(plpgsql)
---
this methold have low efficiency, when the records is large, it will
become slow, so someone can tell me some high efficiency way???
thanks.
On Fri, 2008-09-19 at 16:51 +0800, Yi Zhao wrote:
> hi all:
> I have a table with columns(>2) named "query", "
Yi Zhao <[EMAIL PROTECTED]> schrieb:
> hi all:
> I have a table with columns(>2) named "query", "pop", "dfk".
> what I want is:
> when I do some select, if the column "query" in result records have
> duplicate value, I only want the record which have the maximum value of
> the "pop".
>
> for exa
William Garrison wrote:
> I have been optimizing my pg_restores (postgres 8.2.9 on Windows) and I
> am confused by some of the results I get when combining various
> command-line options.
>
> The -c option for "clean" does not do DROP IF EXISTS statements, it just
> does DROP. This results in an
hi all:
I have a table with columns(>2) named "query", "pop", "dfk".
what I want is:
when I do some select, if the column "query" in result records have
duplicate value, I only want the record which have the maximum value of
the "pop".
for example, the content of table:
query pop dfk
---
The INSERT and DELETE TG_OPs are straightforward (the simplest solution
for these is that the existence of the primary key can be checked in the
other table), however the UPDATE handler is really confusing.
Is it possible for a trigger function to know where an UPDATE originated
(user vs trigger)?
I have been optimizing my pg_restores (postgres 8.2.9 on Windows) and I
am confused by some of the results I get when combining various
command-line options.
The -c option for "clean" does not do DROP IF EXISTS statements, it just
does DROP. This results in an error if the object does not exi
33 matches
Mail list logo
