I can.
-Original Message-
From: Dave Page [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2008 3:50 PM
To: Chan, Keith (LESA IT)
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #4041: error in Application Stack Builder
On Mon, Mar 17, 2008 at 10:15 PM, keith chan <[EMAIL PROTECTE
Mike Leahy wrote:
> Is this actually a bug, or is there a specific reason that the pgxs
> files omitted in the windows installer? I noticed the 8.3.1 installer
> has been posted (as the updates had appeared on my linux machines). From
> what I can tell, the 8.3.1 version of the win32 installe
Hi, all !
i'm find the problem.
src/backend/utils/mb/conversion_procs/cyrillic_and_mic/cyrillic_and_mic.c
does not have cyrillic letter 'IO' in ISO-8859-5 to mule internal code
translation table (function iso2mic(const unsigned char *l, unsigned char *p,
int len)). this is bug, because it is wi
Added to TODO:
* Allow SSL key file permission checks to be optionally disabled when
sharing SSL keys with other applications
http://archives.postgresql.org/pgsql-bugs/2007-12/msg00069.php
---
Simon Arlott wrote:
>
>
On Mon, Mar 17, 2008 at 10:15 PM, keith chan <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 4041
> Logged by: keith chan
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.3
> Operating system: Windows XP with SP2
> De
The following bug has been logged online:
Bug reference: 4041
Logged by: keith chan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3
Operating system: Windows XP with SP2
Description:error in Application Stack Builder
Details:
I did followings
1. click Star
Is this actually a bug, or is there a specific reason that the pgxs
files omitted in the windows installer? I noticed the 8.3.1 installer
has been posted (as the updates had appeared on my linux machines).
From what I can tell, the 8.3.1 version of the win32 installer is still
missing pgxs.mk
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> BTW while reading the psql manpage I noticed this statement:
>A popular application of this facility is to refer to the last
>inserted OID in subsequent statements to build a foreign key
>scenario.
> (This refers to :foo inter
Am Montag, 17. März 2008 schrieb Mika Fischer:
> Ideally, psql should provide an option --no-password which would cause it
> to never promt for a password, and in case one is needed, fail as if a
> wrong one was given.
Something like ssh's BatchMode would be nice.
--
Sent via pgsql-bugs mailing
Peter Eisentraut wrote:
> Am Montag, 17. März 2008 schrieb Tom Lane:
> > It's not, IMHO. You don't even know if the local database is where the
> > user is intending to connect to. Moreover this presupposes some rather
> > obsolete ideas about what connection parameters might need to be given
> >
Tom Lane [2008-03-17 10:48 -0400]:
> Martin Pitt <[EMAIL PROTECTED]> writes:
> > if (PQstatus(pset.db) == CONNECTION_BAD &&
> > PQconnectionNeedsPassword(pset.db) &&
> > - password == NULL &&
> > + password == NULL && !getenv("PGPA
Am Montag, 17. März 2008 schrieb Tom Lane:
> It's not, IMHO. You don't even know if the local database is where the
> user is intending to connect to. Moreover this presupposes some rather
> obsolete ideas about what connection parameters might need to be given
> on the command line.
"psql " to
* Tom Lane <[EMAIL PROTECTED]> [2008-03-17 14:44]:
> "Mika Fischer" <[EMAIL PROTECTED]> writes:
> > I'm currently working on the bash-completion package. The problem with
> > postgresql is that psql cannot safely be called because there is no way to
> > know whether it will prompt for a password an
* Alvaro Herrera <[EMAIL PROTECTED]> [2008-03-17 15:43]:
> Hmm, why do you need to connect to a database? Some time ago I came up
> with this:
>
> _postgres()
> {
> local cur;
> COMPREPLY=()
> cur=${COMP_WORDS[COMP_CWORD]}
> prev=${COMP_WORDS[COMP_CWORD-1]}
>
* Tom Lane <[EMAIL PROTECTED]> [2008-03-17 15:28]:
> Mika Fischer <[EMAIL PROTECTED]> writes:
> > What the current code does is:
> > Run "psql -l" to get the list of local databases, and
> > run "psql -qtc 'select usename from pg_user' template1" to get the list
> > of users. If this fails the syst
Mika Fischer <[EMAIL PROTECTED]> writes:
> * Tom Lane <[EMAIL PROTECTED]> [2008-03-17 15:28]:
>> Something that might be more useful is to see if there's a connection
>> service file
>> http://developer.postgresql.org/pgdocs/postgres/libpq-pgservice.html
>> and offer the names of service entries in
Martin Pitt <[EMAIL PROTECTED]> writes:
> if (PQstatus(pset.db) == CONNECTION_BAD &&
> PQconnectionNeedsPassword(pset.db) &&
> - password == NULL &&
> + password == NULL && !getenv("PGPASSWORD") &&
> !
Mika Fischer wrote:
> I'm currently working on the bash-completion package. The problem with
> postgresql is that psql cannot safely be called because there is no way to
> know whether it will prompt for a password and there is also no way to avoid
> the prompt.
Hmm, why do you need to connect to
"amnuay" <[EMAIL PROTECTED]> writes:
> when I user function makeline_garray (PostGIS1.3 GEOS 3.0)
> Server return
> server closed the connection unexpectedly
You need to report this to the PostGIS people.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs
On Mon, Mar 17, 2008 at 7:34 PM, Martin Pitt <[EMAIL PROTECTED]> wrote:
> Mika Fischer [2008-03-17 10:19 +]:
> > Description:psql should provide option to not prompt for
> password
> > Details:
> >
> > Hi,
> >
> > I'm currently working on the bash-completion package. The problem with
>
Mika Fischer <[EMAIL PROTECTED]> writes:
> What the current code does is:
> Run "psql -l" to get the list of local databases, and
> run "psql -qtc 'select usename from pg_user' template1" to get the list
> of users. If this fails the system users are used for completion.
> I'm not at all a Postgre
Mika Fischer [2008-03-17 10:19 +]:
> Description:psql should provide option to not prompt for password
> Details:
>
> Hi,
>
> I'm currently working on the bash-completion package. The problem with
> postgresql is that psql cannot safely be called because there is no way to
> know whe
"Mika Fischer" <[EMAIL PROTECTED]> writes:
> I'm currently working on the bash-completion package. The problem with
> postgresql is that psql cannot safely be called because there is no way to
> know whether it will prompt for a password and there is also no way to avoid
> the prompt.
> Needless t
Hi, all !
I can't convert with convert(bytea, name, name)::bytea from 'iso-8859-5'
to 'windows-1251' or any other cyrillic 8-bit encoding.
seb=> show client_encoding ;
client_encoding
-
UTF8
seb=> show server_encoding;
server_encoding
-
UTF8
seb=> select ver
The following bug has been logged online:
Bug reference: 4040
Logged by: Mika Fischer
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.0
Operating system: Ubuntu Linux 8.4 beta
Description:psql should provide option to not prompt for password
Details:
Hi,
I
The following bug has been logged online:
Bug reference: 4039
Logged by: amnuay
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.0
Operating system: Redhat RHEL4
Description:server closed the connection when use function
"makeline_garray"
Details:
when I use
26 matches
Mail list logo
