Patch for getaddrinfo.c to recognize ipv6 addresses.Used inet_pton to
achieve that.On machines that don’t have getaddrinfo function, Client
authenciation failsfor ipv6 addresses if pgsql uses getaddrinfo implemented
in this.This is a fix for that.Rajesh R--This space
intentionally left non-b
Albert Chin <[EMAIL PROTECTED]> writes:
> On Sun, Feb 19, 2006 at 11:32:53PM -0500, Tom Lane wrote:
>> Would you try the patch proposed at
>> http://archives.postgresql.org/pgsql-patches/2006-01/msg00299.php
> Works fine on Tru64 UNIX 4.0D and 5.1.
OK, applied to HEAD and 8.1. I'm feeling a bit
On Sun, Feb 19, 2006 at 11:32:53PM -0500, Tom Lane wrote:
> Albert Chin <[EMAIL PROTECTED]> writes:
>
> > The solution is to either revert to the 8.1.1 code (my recommendation)
> > or check for ngetaddrinfo. The latter is a crude hack though.
>
> Hm, I think both of us are confused: me because I
On Tue, 21 Feb 2006, Michael Glaesemann wrote:
On Feb 20, 2006, at 0:41 , Tom Dunstan wrote:
Andrew Dunstan wrote:
my *son* (whose name is Tom btw ;-) ) was 3 yrs old in '82 ...
So, as you were responsible for me at the time, the fact that *I* don't
have any usenet posts back that far is
On Feb 20, 2006, at 0:41 , Tom Dunstan wrote:
Andrew Dunstan wrote:
my *son* (whose name is Tom btw ;-) ) was 3 yrs old in '82 ...
So, as you were responsible for me at the time, the fact that *I*
don't have any usenet posts back that far is clearly your fault.
My goodness. When I first
On Mon, 20 Feb 2006, Tom Lane wrote:
> "Sergey E. Koposov" <[EMAIL PROTECTED]> writes:
> > I've recently proposed a patch
> > http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php
> > to fix an old problem with dropped columns, but recently
> > http://archives.postgresql.org/pgsql-p
"Marko Kreen" <[EMAIL PROTECTED]> writes:
> On 2/20/06, Tom Lane <[EMAIL PROTECTED]> wrote:
>> This seems like a pretty bad idea: if the SPI_connect fails you lose
>> control without having unwound the subtransaction. That's unlikely,
>> but still wrong.
> But if I want the error to reach upper t
"Sergey E. Koposov" <[EMAIL PROTECTED]> writes:
> I've recently proposed a patch
> http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php
> to fix an old problem with dropped columns, but recently
> http://archives.postgresql.org/pgsql-patches/2006-02/msg00246.php
> Neil Conway have d
Martijn van Oosterhout wrote:
> The input file could be simply line based. Attached is a simple
> script that takes the input below and produces something resembling
> what you suggested. It wouldn't be too hard to get it to produce
> multiple output formats and dump the output to different files..
On Mon, Feb 20, 2006 at 09:03:29AM +0100, Michael Paesold wrote:
> Elein wrote:
> >http://www.varlena.com/GeneralBits/128.php
> >
> >Known Problems and Issues:
> >
> > * Creating the table with an email PRIMARY KEY did not use our
> >comparison function. It was necessary to create a unique index
I decided to move the discussion to -hackers ...
Hello All,
I've recently proposed a patch
http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php
to fix an old problem with dropped columns, but recently
http://archives.postgresql.org/pgsql-patches/2006-02/msg00246.php
Neil Conway h
Hi Guys,
Does anyone here have time to chime into this
thread on LQ and give a nice spiel about PG? :)
http://www.linuxquestions.org/questions/showthread.php?t=409045
Cheers,
Andrej
---(end of broadcast)---
TIP 4: Have you searched our list archi
On 2/20/06, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Marko Kreen" <[EMAIL PROTECTED]> writes:
> > BeginInternalSubTransaction(NULL);
> > res = SPI_connect();
> > if (res < 0)
> > elog(ERROR, "cannot connect to SPI");
> This seems like a pretty bad idea: if the SPI_con
Andrew Dunstan wrote:
my *son* (whose name is Tom btw ;-) ) was 3 yrs old in '82 ...
So, as you were responsible for me at the time, the fact that *I* don't
have any usenet posts back that far is clearly your fault.
:)
Tom
---(end of broadcast)-
On 2006-02-20, Tatsuo Ishii <[EMAIL PROTECTED]> wrote:
> In further investigation, Akio Ishida found this kind of attack is
> possible even with EUC_JP/UTF-8.
How?
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast
> > Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> > > I suggest that PQescapeString() should have a parameter to specify the
> > > encoding of "to".
> >
> > You mean the encoding of "from", no?
>
> Oops, "from", yes.
>
> > But actually I'd argue that
> > letting the client programmer supply the enc
"Marko Kreen" <[EMAIL PROTECTED]> writes:
> BeginInternalSubTransaction(NULL);
> res = SPI_connect();
> if (res < 0)
> elog(ERROR, "cannot connect to SPI");
> PG_TRY();
> {
> res = SPI_execute("update one row", false, 0);
> SP
Albe Laurenz wrote:
> We sometimes need to move a database from one machine to another
> (hardware old/broken, upgrades, etc.). Now whenever a database is
> moved to a different computer, all the clients have to address the
> database at the new hostname.
>
A lower-tech solution is:
http://
Stephen Frost wrote:
* Martijn van Oosterhout (kleptog@svana.org) wrote:
Perhaps you should look into pg_service.conf. It's a configuration file
such that in your connect line you can say:
PQconnect("service=production");
and in the config file you say:
[production]
host=db1
port=5434
dbn
I want to update one row from possibly several backends. In case
of SERIALIZABLE transactions, the update command may fail. To
hide it from calling transaction, I use a subtransaction and try
to catch and hide the error.
With help of plpgsql source, I wrote following code that _seems_
to work. B
Martijn van Oosterhout writes:
> This test is different, it checks that getaddrinfo has four args.
If it doesn't, we don't wanna use it anyway ...
regards, tom lane
---(end of broadcast)---
TIP 1: if posting/reading through
Am Montag, 20. Februar 2006 14:33 schrieb Adam Witney:
> That seems quite handy to know! can these be saved anywhere such that I
> don't have to run the \set <...> command every session?
~/.psqlrc
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of br
On Mon, Feb 20, 2006 at 02:36:42PM +0100, Albe Laurenz wrote:
> $ psql -h host -p port -d database .
> you'd use something like
> $ psql -N dbalias ...
> and the client would perform a lookup on the LDAP server and
> retrieve host name, port and database name.
I suggest you look at pgpool, whi
> ALTER USER bob SET search_path ...?
>
Sorry I didn't mean the search_path example, but I was thinking I could
setup a short cut for a common query, eg:
\set logins
:logins
Could save this such that the short cut is available every time I open psql?
Thanks
Adam
--
This message has bee
ALTER USER bob SET search_path ...?On 2/20/06, Adam Witney <[EMAIL PROTECTED]> wrote:
On 20/2/06 1:26 pm, "Peter Eisentraut" <[EMAIL PROTECTED]> wrote:> Am Montag, 20. Februar 2006 14:15 schrieb Q Beukes:>> Hey, This might not be much, but can there maybe be a future feature for
>> having a sho
* Martijn van Oosterhout (kleptog@svana.org) wrote:
> Perhaps you should look into pg_service.conf. It's a configuration file
> such that in your connect line you can say:
>
> PQconnect("service=production");
>
> and in the config file you say:
>
> [production]
> host=db1
> port=5434
> dbname=ma
On Mon, Feb 20, 2006 at 02:36:42PM +0100, Albe Laurenz wrote:
> Dear developers of PostgreSQL!
>
> We (City of Vienna) have many Oracle databases, but plan to use
> PostgreSQL for our future database installations as much as possible.
> The following idea is inspired by Oracle.
>
> We sometimes n
Dear developers of PostgreSQL!
We (City of Vienna) have many Oracle databases, but plan to use
PostgreSQL for our future database installations as much as possible.
The following idea is inspired by Oracle.
We sometimes need to move a database from one machine to another
(hardware old/broken, upg
On 20/2/06 1:26 pm, "Peter Eisentraut" <[EMAIL PROTECTED]> wrote:
> Am Montag, 20. Februar 2006 14:15 schrieb Q Beukes:
>> Hey,
>>
>> This might not be much, but can there maybe be a future feature for
>> having a shortcut to "set search_path='schema-name';"
>> similiar to \c dbname ??
>
> pei=#
Am Montag, 20. Februar 2006 14:15 schrieb Q Beukes:
> Hey,
>
> This might not be much, but can there maybe be a future feature for
> having a shortcut to "set search_path='schema-name';"
> similiar to \c dbname ??
pei=# \set X 'set search_path = '
pei=# :X public;
SET
pei=# show search_path;
sear
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey,
This might not be much, but can there maybe be a future feature for
having a shortcut to "set search_path='schema-name';"
similiar to \c dbname ??
Thx
Quintin Beukes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using
Hello all .
Can anyon eplz tell me how memory profiling is done
in postgreSQL. I read on a website I don't remember now that postgres
creates a file pgsql/data/base/dbname and stores memory profiling
information in it. postgres creates a folder with integer name in
pgsql/base/ and in that folde
Elein wrote:
http://www.varlena.com/GeneralBits/128.php
Known Problems and Issues:
* Creating the table with an email PRIMARY KEY did not use our
comparison function. It was necessary to create a unique index which
explicitly used the email operator class.
* ORDER BY requires USING op
33 matches
Mail list logo
