On 11/13/09 5:26 AM, Juan Backson wrote:
Hi,
I had a chat with Suzuki Hironobu (pgmemcached maintainer) earlier this
year and we pretty much decided that pgmemcache was the way to go after
which Suzuku wrote a large patch to make it also support libmemcached
behaviors and earlier PostgreSQL's.
Im trying to set up pgbouncer. Installation seemed to go well but when
I try...
$ pgbouncer -d pgbouncer.ini
I get an error...
2009-11-13 02:02:35.170 7245 ERROR broken auth file
2009-11-13 02:02:35.170 7245 LOG File descriptor limit: 1024 (H:1024),
max_client_conn: 100, max fds possible: 110
H
Dear all,
I am trying to install the postgres8.2.14 via the RPM; however the install
directory is default to the following folder
- Executables : /usr/bin
- Libraries : /usr/lib
- Documentation : /usr/share/doc/postgresql-x.y.z ,
/usr/share/doc/postgresql-x.y.z/contrib
- Contrib :
Nick wrote:
> Im trying to set up pgbouncer. Installation seemed to go well but when
> I try...
>
> $ pgbouncer -d pgbouncer.ini
>
> I get an error...
>
> 2009-11-13 02:02:35.170 7245 ERROR broken auth file
It's complaining about your auth file, rather than pgbouncer.ini
> Here is my pgbouncer
Below is sample pgbouncer.ini file.
postgres = host=127.0.0.1 port=5432 dbname=postgres
postgres = host=127.0.0.1 dbname=postgres
postgres = host=127.0.0.1 port=5432 user=sam password=jas
client_encoding=UNICODE datestyle=ISO connect_query='SELECT 1'
logfile = pgbouncer.log
pidfile = pgbouncer.p
Hi all,
I am new to Postgres and am interested in XLOG's implementation
details. I browsed around the source code, and saw that the particular
function that appends XLOG entries is called from multiple places
(heap, indexes, transaction subsystem, and so forth). Seeing this, I
became particularly
weixiang tam wrote:
> I am trying to install the postgres8.2.14 via the RPM;
> however the install directory is default to the following folder
>
>
>
> * Executables : /usr/bin
> * Libraries : /usr/lib
> * Documentation : /usr/share/doc/postgresql-x.y.z ,
> /usr/share/doc/postgre
Hi,
I am new to user lists, so please don't be to hard on me if I am doing
anything wrong.
I have been running a postgres database with slony replication for some
years now as a backend for a apache webserver and lately some mono
(.net) programs. The database and webserver is running on a Ubuntu
Dear programmers,
I am using the handy LISTEN/NOTIFY mechanism provided by PostgreSQL in my
client application, written in C with libpq. It is a simple
single-threaded single-process client (thanks to the NOTIFIcation!),
waiting for the notification using select() call with finite timeout.
Af
Gunnar Sønsteby wrote:
> Hi,
>
> I am new to user lists, so please don't be to hard on me if I am doing
> anything wrong.
>
> I have been running a postgres database with slony replication for some
> years now as a backend for a apache webserver and lately some mono
> (.net) programs. The databas
Hi:
Does PG support the notion of a colum alias? I'm not talking about "select foo
as fii", I'm thinking more along the lines of supporting 2 different names
for the same column. For example, a tablle has a column named
"social_security_number". Queries may ask for this column as define
On Fri, Nov 13, 2009 at 9:22 AM, Marek Peca wrote:
> Please, can you tell me, what am I doing wrong?
I have very similar code written in Perl, and I never observe failures
like you see after a timeout on the select call. This code has been
in production on farily busy systems for several years n
Richard Huxton writes:
> Gunnar Sønsteby wrote:
>> 2009-11-12 06:11:51 CET INSERTERROR: cache lookup failed for type 19218
> So - something is trying to access a slony type via its old OID rather
> than its new one (or something like that). Not sure what this would be,
> since the drop-schema +
On Fri, Nov 13, 2009 at 6:33 AM, Gauthier, Dave wrote:
> Does PG support the notion of a colum alias?
No, the closest thing would be alias names from a VIEW.
> Is there a way to assign 2 different names for the same column to support a
> situation like above?
No.
> I was thinking that a view
Tom Lane wrote:
> Richard Huxton writes:
>> Gunnar Sønsteby wrote:
>>> 2009-11-12 06:11:51 CET INSERTERROR: cache lookup failed for type 19218
>
>> So - something is trying to access a slony type via its old OID rather
>> than its new one (or something like that). Not sure what this would be,
>
Dear Vick,
I have very similar code written in Perl, and I never observe failures
like you see after a timeout on the select call. This code has been
in production on farily busy systems for several years now.
can you tell me, which libpq and server versions you are running on?
I have constan
Richard Huxton wrote:
> Tom Lane wrote:
> > Richard Huxton writes:
> >> Gunnar Sønsteby wrote:
> >>> 2009-11-12 06:11:51 CET INSERTERROR: cache lookup failed for type 19218
> >
> >> So - something is trying to access a slony type via its old OID rather
> >> than its new one (or something like t
On Fri, Nov 13, 2009 at 1:34 AM, Matt Sanchez wrote:
> Hello,
>
> Suppose I have a table:
> create table foo ( id int4, name varchar(50) );
>
> I want to prepare and execute in binary mode:
> select name from foo where id in ($1);
>
> Execute works when I have a single value for $1,
Hi,
Thank you very much for your answers.
I have backups, lot of backups, so it should be possible restore the database
on a testmachine and start digging.
Best regards
Gunnar
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://w
2009/11/12 Dave Page
> On Thu, Nov 12, 2009 at 12:18 AM, Thom Brown wrote:
>
> > I second that. I wasn't sure quite what to expect, but it was very
> > well organised and executed. And thanks to our French hosts whose
> > hard work really paid off too! The talks were excellent, especially
> >
Merlin Moncure wrote:
On Fri, Nov 13, 2009 at 1:34 AM, Matt Sanchez wrote:
Hello,
Suppose I have a table:
create table foo ( id int4, name varchar(50) );
I want to prepare and execute in binary mode:
select name from foo where id in ($1);
Execute works when I have a single valu
Marek Peca writes:
> The problem: most of time, everything works fine, hundreds of successful
> or even timed-out selects() get handled without any problem. But time to
> time (eg. after several hours), the select() call returns with a timeout
> and then, a request to the opened PQconn (simple
On Fri, 13 Nov 2009, Tom Lane wrote:
What that sounds like is a network-level problem. In particular, if
there's a NAT-capable router between your client and server machines,
it's probably dropping the connection after a certain period of
inactivity.
Yes, it probably is. The connection goes th
Marek Peca writes:
> However: I can not get the point, why does the PQexec() (or PQstatus() at
> least) hang, instead of returning some error? I know, that situation with
> broken TCP connection may involve long timeouts, but it could return at
> least after several minutes, couldn't it?
"Seve
"Several hours" might be more like it.
Better than infinity, of course.
How long have you waited?
Two days, for example.
In any case, that complaint should be directed to your kernel vendor
not us. We do not control how long the TCP stack waits before declaring
the connection dead.
Wel
Marek Peca writes:
>> In any case, that complaint should be directed to your kernel vendor
>> not us. We do not control how long the TCP stack waits before declaring
>> the connection dead.
> Well, this is what I wanted to hear. So if I call PQstatus() or PQexec(),
> the libpq sends some data t
On Fri, 13 Nov 2009, Tom Lane wrote:
Well, if you *never* get a failure, then yeah I think you have a broken
TCP stack. The default timeouts on this sort of thing are annoyingly
long, but they aren't infinite.
Yes, this is the case. Both ends are running on GNU/Linux system and I
expect that
On Fri, Nov 13, 2009 at 10:07 AM, Marek Peca wrote:
> Dear Vick,
>
>> I have very similar code written in Perl, and I never observe failures
>> like you see after a timeout on the select call. This code has been
>> in production on farily busy systems for several years now.
>
> can you tell me, w
weixiang tam wrote:
As we are bundling the postgresql db as our product release, we would
like to keep the Postgres executable dir, Data Dir under our product
folder. In this case, could I know whether I can customize the install
directory when i do the RPM installation?
What you'd probably lik
Greg Smith writes:
> weixiang tam wrote:
>> As we are bundling the postgresql db as our product release, we would
>> like to keep the Postgres executable dir, Data Dir under our product
>> folder. In this case, could I know whether I can customize the install
>> directory when i do the RPM inst
weixiang tam wrote on 13.11.2009 10:16:
Dear all,
I am trying to install the postgres8.2.14 via the RPM; however the
install directory is default to the following folder
* Executables : /usr/bin
* Libraries : /usr/lib
* Documentation : /usr/share/doc/postgresql-x.y.z ,
/usr/
Tom Lane wrote:
The real problem that I think the OP hasn't considered is whether
his "bundled" RPM package isn't going to conflict with a preinstalled
postgresql RPM. Relocating the RPM, either dynamically as you suggest
or by just changing the install paths while building it, isn't a very
pala
Probably the following might have been asked before, but I've been
searching the web for the following problem for 2 days already:
I need to install an end-user application which demands 2 postgresql
users each owning its own database.
One user+database is used for a data management system (I c
On Nov 13, 2009, at 8:05 PM, Reno Bladergroen wrote:
> Probably the following might have been asked before, but I've been searching
> the web for the following problem for 2 days already:
> I need to install an end-user application which demands 2 postgresql users
> each owning its own database
Thanks Richard, I updated my users.txt file to include quotes (it
didn't) which fixed the broken auth file error, but now im getting
this...
1518 ERROR unconfigured_file: No such file or directory
which repeats over and over again when I try
pgbouncer -v pgbouncer.ini
I updated my ini file to
__
Some time ago, a confirmation token was sent to you because of the
following request:
"unregister pgsql-general@postgresql.org"
It was sent for the following reason(s):
The default rule says that the "unregister" commandmust be confirmed by
the person affected by the command.
Th
36 matches
Mail list logo
