ation file.
You must specify the --config-file or -D invocation option or set the
PGDATA environment variable.
$ /usr/lib/postgresql/9.2/bin/postmaster --version
postgres (PostgreSQL) 9.2.2
bye,
-christian-
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make chang
* Christian Ullrich wrote:
I think I have a pretty good fix: Early in configure, see if the linker
understands --no-copy-dt-needed-entries, or alternatively
--no-add-needed (which is a deprecated name for the same thing). This is
the "light" version of --as-needed: It does not discar
ely easily, by first installing the
binutils port and then installing Postgres with CFLAGS=-B/usr/local/bin .
--
Christian
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
61 #: pg_basebackup.c:127
62 #, c-format
63 msgid " -F, --format=p|t output format (plain, tar)\n"
64 msgstr " -F, --format=c|t|p Ausgabeformat (plain, tar)\n"
pg_basebackup does not support "c" format.
The other three translations are corre
x for queries. I'll see about fixing this in HEAD, although
> my initial guess is that it will be too invasive to back-patch.
I didn't recognized the exclusion constraint feature before. But it looks
interesting.
Thank you for your effort.
Christian
--
NEU: FreePhone - 0ct/min Handys
On 03/04/2011 12:58 AM, Tom Lane wrote:
> I wrote:
>> Christian Kastner writes:
>>> Using libpq 9.0.3, when an SSL connection is attempted from a client
>>> whose EUID is not in a password database, the connection fails because
>>> the home directory ca
ilure
previously only occurred when sslmode was "verify-*", otherwise the
missing home dir was ignored. Now, it always fails.
It was pointed out to me that the client-side SSL stuff changed in
9.0.3, so this might be entirely valid. I was just a little suprising.
Regards,
Christian
--
The following bug has been logged online:
Bug reference: 5512
Logged by: Christian Hansen
Email address: chanse...@btinternet.com
PostgreSQL version: 8.4.4
Operating system: Windows XP
Description:Password error message
Details:
I need to set up a programme
The following bug has been logged online:
Bug reference: 5161
Logged by: christian david
Email address: chrisdav8...@hotmail.com
PostgreSQL version: 08_02_0400
Operating system: windows xp
Description:tome nota del siguiente error un error ha ocurrido 999
Details
The following bug has been logged online:
Bug reference: 5107
Logged by: Christian DUPONT
Email address: christian.dup...@cegelec.com
PostgreSQL version: 8.3
Operating system: RHEL 5
Description:Lock never released
Details:
Hi,
I use slony 1 v 1.2.14.
After an
uld I do something to close the bug report?
--
Med venlig hilsen / Best regards
Christian Iversen
Sikkerhed.org ApS
Fuglebakkevej 88 E-mail: supp...@sikkerhed.org
1. sal Web: www.sikkerhed.org
DK-2000 Frederiksberg Direkt
The following bug has been logged online:
Bug reference: 4150
Logged by: Christian Lippuner
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.7/8.3.1
Operating system: Linux
Description:ecpg: update/insert of array data does not work anymore
since Version 8.2
haring" enabled? If so, the client user is always
authenticated as Guest. The Guest user is usually disabled, which makes
authentication fail.
For details see <http://www.ngssoftware.com/papers/database-on-xp.pdf>.
--
Christian Ullrich . Expect a letter from a friend who will ask
* Tom Lane wrote:
> "Christian Ullrich" <[EMAIL PROTECTED]> writes:
>> My mistake. I should have been using the heimdal port instead of the
>> ancient release in the base system.
>
> So, how ancient is it? Is there any reason we should try to make
> -
* Christian Ullrich wrote:
> The following bug has been logged online:
[...]
> Description:configure --with-gssapi fails
> ./configure --with-gssapi fails when checking for
> gss_init_sec_context.
My mistake. I should have been using the heimdal port instead of the
ancien
The following bug has been logged online:
Bug reference: 3927
Logged by: Christian Ullrich
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.0
Operating system: FreeBSD 6.3
Description:configure --with-gssapi fails
Details:
./configure --with-gssapi fails
The following bug has been logged online:
Bug reference: 3814
Logged by: Christian Ullrich
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3beta4
Operating system: Windows 2003
Description:initdb fails when not run from installation directory
Details:
initdb
* Magnus Hagander wrote:
Christian Ullrich wrote:
psql tells me about an "invalid frontend message type 112". Most of the
time, that error comes as the first line of output from psql (above the
"Welcome to" line), sometimes it is displayed later:
Does it work if you r
The following bug has been logged online:
Bug reference: 3750
Logged by: Christian Ullrich
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3-beta2
Operating system: Windows Server 2003
Description:Invalid frontend message type 112
Details:
I'm runnin
The following bug has been logged online:
Bug reference: 3605
Logged by: Christian PANEL
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: Windows XP
Description:impossible loading
Details:
I have tried many mirrors sites to download
The following bug has been logged online:
Bug reference: 3382
Logged by: Christian Andritzky
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.13
Operating system: Windows XP SP2
Description:Service fails to start with option -w
Details:
The pgsql-8.0 Win32
I Think that your problem is: test.mytable() <> test.mytable, why your
table name include --> ()
On Fri, 2007-06-08 at 16:59 +, Kevin Neufeld wrote:
> The following bug has been logged online:
>
> Bug reference: 3377
> Logged by: Kevin Neufeld
> Email address: [EMAIL PROTE
Hi,
On Thu, 17 May 2007, Tom Lane wrote:
Christian Kratzer <[EMAIL PROTECTED]> writes:
It's not that simple though. The ipv6 stack will propably not allow
users to build sockets from addresses in link local scope from a
specific interface to a server bound to a global address, ::1
we hack the server to suppress any
%-foo found in the result of getnameinfo()?
Not sure what that would buy us. Stripping the scope from the address
does not seem the right thing to do.
Extending the generic inet type with scoped addresss is another question.
Greetings
Christian
--
Christian K
Hi,
On Thu, 17 May 2007, Andrew Sullivan wrote:
On Thu, May 17, 2007 at 07:29:47PM +0200, Christian Kratzer wrote:
supporting scoped addresses could have their uses but then again
theres nothing stopping you to bind multiple global ipv6 addresses
to your loopback interface which would work
Hi,
On Thu, 17 May 2007, Andrew Sullivan wrote:
On Thu, May 17, 2007 at 06:42:39PM +0200, Christian Kratzer wrote:
of a specific interface. This is why bsd based oprating systems append
%ifname to the address so that they know which Interface this address
Oh, I forgot about that wart in
r details.
There is propbaly not much point in using link local addreses for postgres.
You should have global ipv6 prefix on your interfaces to really make use
of ipv6.
Greetins
Christian
--
Christian Kratzer CK Software GmbH
Email: [EMAIL PROTECTED] S
I'm sorry Tom, you are right.
Atentamente,
Soluciones Integrales GIS C.A (SIGIS)
Christian Gonzalez
[EMAIL PROTECTED]
-Mensaje original-
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
En nombre de Tom Lane
Enviado el: Miércoles, 18 de Abril de 2007 01:24 p.m.
Para: Chri
The following bug has been logged online:
Bug reference: 3235
Logged by: Christian Gonzalez
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.1
Operating system: Red Hat 4.1.1-30
Description:Partitioning has problem with timestamp and timestamptz
data types
The following bug has been logged online:
Bug reference: 3236
Logged by: Christian Gonzalez
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.1
Operating system: Red Hat 4.1.1-30
Description:Partitioning has problem with timestamp and timestamptz
data type
D::Pg) if you have to pass
parameters in the SQL string to use partial indexes.
I hope you are not relying on prepared statements as your only
defense against sql code injection.
Greetings
Christian
--
Christian Kratzer [EMAIL PROTECTED]
CK Software GmbH
The following bug has been logged online:
Bug reference: 2366
Logged by: Christian Holtje
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.8
Operating system: Ubuntu 5.10
Description:Timestamptz data type is inaccurate
Details:
I don't know what'
The following bug has been logged online:
Bug reference: 1854
Logged by: Christian Almeida
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows XP SP2
Description:SQL Bug
Details:
Should this sql work?
I just picked 3 tables from
The following bug has been logged online:
Bug reference: 1728
Logged by: Christian Mercure
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows XP
Description:unable to connect from other stations
Details:
I am evaluating backend
Hi there,
i'd like to test PG8-RC1 (postgresql-8.0.0-rc1.msi) but installation fails.
When starting msi file from a cmd i've to select the language (EN, DE, PORT)
after this there pops up a small window (maybe something like the msi
installation
progress) that hides immediately.
Installation i
.i686.rpm" for both,
my output command is:
/usr/lib/pgsql/plperl.so
/usr/lib/pgsql/plpython.so
the plctl.so doesn't exist.
Regards, Christian Gonzalez
-Mensaje original-
De: Tom Lane [mailto:[EMAIL PROTECTED]
Enviado el: Miércoles, 08 de Septiembre de 2004 03:37 p.m.
Para: Chr
Tom Lane wrote:
Use a later release.
Seriously, 7.1.* is not supported anymore. There are extremely serious
known bugs in it that will never be fixed. I can't imagine a reason for
you to be trying to build it rather than something more current.
actually, we are upgrading our system the previously
Hi,
i was trying to install postgres 7.1.3 on Redhat 9, using perl 5.8.0-88.3,
./configure --enable-multibyte --enable-odbc --with-perl --with-java
--with-tcl
but make fails on plperl:
gcc -c -I../../../src/include -D_REENTRANT -D_GNU_SOURCE
-DTHREADS_HAVE_PIDS -DDEBUGGING -fno-strict-aliasing
sts (9 GB, right now and has been up for 3 days).
Maybe I'll try to lower shared buffers...
Christian
P.S.: Running 7.4.2 on OSX 10.3.4 with 4.5 GB RAM.
On Jun 8, 2004, at 6:53 AM, Tom Lane wrote:
Christian van der leeden <[EMAIL PROTECTED]> writes:
this is just a me too message.
Neit
th around 1.6 million rows.
Thanks
Christian
On May 21, 2004, at 10:15 PM, [EMAIL PROTECTED] wrote:
Hi,
we have a postgresql 7.4 database server on an X Server with Mac OS 10.3.3, 7F45
The server possess two CPU's, 4 Gb in memory, and an adequate space on disk.
The service run fine
e | not null
CU
Christian
On Thursday, August 7, 2003, at 04:23 PM, Tom Lane wrote:
Christian van der Leeden <[EMAIL PROTECTED]> writes:
the reason for this misbehaviour was an invalid timestamp value.
I've tried to dump/restore the db and the restore choked on a
"incor
elimnated the lines containing this value, and successfully
restoring the db, the transcript below worked fine (w/o/ problems)
Don't know how the values got there in the first place (everything in
the db was
created through a java app through JDBC)
Christian
P.S.: The db was created with 7
*) from delivery where "creation_date"
<= TIMESTAMP '2003-04-01 00:00:00' and "creation_date" > TIMESTAMP
'2003-03-01 00:00:00';
count
---
10371
(1 row)
christian
------
Christian van der Leeden
Logi
*) from delivery where "creation_date"
<= TIMESTAMP '2003-04-01 00:00:00' and "creation_date" > TIMESTAMP
'2003-03-01 00:00:00';
count
---
10371
(1 row)
christian
------
Christian van der Leeden
Logi
to have been fixed since I
am experiencing the same problem using 7.3.3.
Is there an easy work around?
Thanks,
Jean-Christian Imbeault
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail c
eport to PHP and pointed this out. Hopefully the developer will see
that this sequence is incorrect EUC-JP and that PHP failed to detect this :)
I *knew* there was nothing wrong with Postgres ;)
Thanks!
Jean-Christian Imbeault
PS I posted to HACKERS a few weeks ago about another bug (a real one
ome from??)
(B
(BCan someone let me know if this truly is a bug in postgres?
(B
(BThanks,
(B
(BJean-Christian Imbeault
(B
(B
(BPS I have also had the error pop up with this string:
(B
(Bsearch_words=%B7%F6%BA%7E
(Bselect id from products where name like '??~'
(BQuery faile
You must have been right about the problem being due to something being
leftover from the old DB because I cannot recreate the problem anymore.
Sorry to have spotted a non-existent bug.
Jc
---(end of broadcast)---
TIP 3: if posting/reading throug
As a follow-up I get an error when dropping plpgsql and then trying to
re-create it ...
$ psql JC -c "drop language plpgsql cascade"
NOTICE: Drop cascades to function cancell_all_li()
NOTICE: Drop cascades to trigger insert_invoices on table invoices
NOTICE: Drop cascades to function update_in
Tom Lane wrote:
>
> I'm still wondering if you are actually invoking a 7.3 server, and not
> an old pre-7.1 one. 'psql -c "select version()"' would tell the tale.
[postgres@localhost work]$ psql JC -c "select version()"
version
--
Tom Lane wrote:
I editing bin/createdb, hard coding the value of PGLIB and createdb then
worked fine.
This is certainly not the correct solution.
I certainly agree. What can I do to pin-point the root cause of the
problem? My environment vars seem to be set correctly so I don't
understand
Don't know if this is a bug or not but ... this query worked under 7.2.1
but doesn't under 7.3RC2. datetime was a built-in function ...
$ psql JC -c "select to_char(datetime(upload_time),'-MM-DD') as
utime from products where id='989000627108' "
ERROR: Function datetime(timestamp without ti
Seems to be a bug in the bin/createdb script. I tried to use the script
as is and got the following error:
$ createlang plpgsql JC
ERROR: stat failed on file '$libdir/plpgsql': No such file or directory
createlang: language installation failed
But my PGLIB path is correct:
$ set | grep PG
PGDA
Sorry if this has been brought up before. I tried searching the archives
at http://archives.postgresql.org/pgsql-bugs/ but it seems the search
function is broke.
Don't know if this is a bug or not but ... this query worked under 7.2.1
but doesn't under 7.3RC2. datetime was a built-in function i
I think you've fixed it. With your patch, and a simple
$ ./configure
$ make
$ make check
# make install
the check works and all tests (except geometry on floating point stuff)
pass; and after installing, I can really hammer the server and it
doesn't hang. Looks like users on Yellow Dog Linux
On Friday, Sep 20, 2002, at 11:30 US/Eastern, Tom Lane wrote:
> Another interesting line of attack would be to try compiling
> src/backend/storage/lmgr/lwlock.c at different optimization levels,
> to see if the problem goes away with less optimization. We saw a
> problem on AIX (if memory serves
On Friday, Sep 20, 2002, at 11:30 US/Eastern, Tom Lane wrote:
> If you are using "make check" then look for
> src/test/regress/tmp_check/data/base/*/core
Thanks. Here it is:
$ gdb src/test/regress/tmp_check/install/usr/local/pgsql/bin/postmaster
src/test/regress/tmp_check/data/base/16556/core
On Thursday, Sep 19, 2002, at 18:33 US/Eastern, Tom Lane wrote:
> David Christian <[EMAIL PROTECTED]> writes:
>> Happy to. Interestingly, when I build with --enable-debug and
>> --enable-cassert, the server doesn't lock up during 'make check', it
>>
On Thursday, Sep 19, 2002, at 17:10 US/Eastern, Tom Lane wrote:
> Could you build with --enable-debug and --enable-cassert (if you didn't
> already), repeat the 'make check' scenario, and then attach to a few of
> the stuck backend processes with gdb and get stack traces from them?
> That would g
Hi, I posted this through the web page but it didn't come over the
list, so I am sending it directly. Hope that's okay.
I am able to get PostgreSQL 7.2.2 built and installed, and postmaster
starts up fine, but when hit with multiple simultaneous connections (2
or more), the server freezes
nohup pg_dump -R -O leemail2 | gzip -c
>/tmp/resp.leemail2_25_6_2002_1_00_pm.sql.gz[avl@bdserver avl]$
Y no se a que se debe.
Atentamente,
Christian Gonzalez.
see attachment
--
Christian Zagrodnick
gocept gmbh & co. kg - schalaunische strasse 6 - 06366 koethen/anhalt
fon. +49 3496 3099114
fax. +49 3496 3099118
mob. +49 173 9078826
mail [EMAIL PROTECTED]
If PostgreSQL failed to compile on your computer or you found a bug that
is likely t
see attachment
--
Christian Zagrodnick
gocept gmbh & co. kg - schalaunische strasse 6 - 06366 koethen/anhalt
fon. +49 3496 3099114
fax. +49 3496 3099118
mob. +49 173 9078826
mail [EMAIL PROTECTED]
If PostgreSQL failed to compile on your computer or you found a bug that
is likely t
tn't be true.
Is this a known bug?
Greetings
Christian Breimann
--
Christian Breimann
[EMAIL PROTECTED] Institut fuer Informatik
Tel.: (+49) 251 - 83 38442 Westfaelische Wilhelms-Universitaet
FAX.: (+49) 251 - 83 33755 Einsteinstr. 62, 48149 Muenster, Germany
-
64 matches
Mail list logo
