The following bug has been logged online:
Bug reference: 6273
Logged by: Justin
Email address: just...@steinhafels.com
PostgreSQL version: 9.1.1
Operating system: Windows Server 2003
Description:Install Error
Details:
On installation, it throws on error stating
On Jan 14, 2010, at 10:44 AM, Tom Lane wrote:
> Justin Pitts writes:
>> On Jan 14, 2010, at 10:16 AM, Tom Lane wrote:
>>> The 100 temp table creations probably will do that just fine.
>
>> Is there a way to verify this?
>
> You could add an elog(LOG, &quo
On Jan 14, 2010, at 10:16 AM, Tom Lane wrote:
> Justin Pitts writes:
>> My guess is that I am not provoking a 'SI queue overrun'
>
> The 100 temp table creations probably will do that just fine.
>
Is there a way to verify this?
>> Am I completely
As difficult as it was to reproduce the bug, I'd like a clear cut regression
test. The use case where it manifested is fairly rare in normal use - server
start after prolonged outage, where the queue of inbound device events is built
up enough to make serialization errors more likely.
On Jan 14
ublic static void main(String... args) throws SQLException,
InterruptedException {
Bug5269Test test = new Bug5269Test();
test.test();
}
}
On Jan 13, 2010, at 10:22 PM, Justin Pitts wrote:
> Sorry for the delay.
>
> I am attempt
Sorry for the delay.
I am attempting to construct a JDBC test case that reproduces the problem.
I have installed the patch and have not seen the crash since.
On Jan 13, 2010, at 11:58 AM, Tom Lane wrote:
> I wrote:
>> After puzzling over this for many hours, I have a theory that seems to
>> fi
The following bug has been logged online:
Bug reference: 5269
Logged by: Justin Pitts
Email address: justinpi...@gmail.com
PostgreSQL version: 8.4.2
Operating system: Debian Lenny 2.6.30-bpo.1-amd-64 kernel
Description:postgres backend terminates with SIGSEGV
Details
The following bug has been logged online:
Bug reference: 4886
Logged by: Justin
Email address: justin.br...@navy.mil
PostgreSQL version: 8.3.7
Operating system: Windows XP
Description:Password Crash
Details:
The % sign included in the password field crashes
rsion in StartupMessage is 1234 and
5679, not 3 and 0, that is the problem, I want to know whether it is the
bug of 8.1.4, or I can do some configuration?
Thanks again for your answer
Thanks,
Justin
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 22, 2008
tdb -h localhost
Output:
Password:
Then enter password, it can log in and do all operation.
Thanks,
Justin
-Original Message-
From: Heikki Linnakangas [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 21, 2008 8:14 PM
To: TIAN Justin
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] error m
s 8.0.3, there is no problem, I don't know why, does it the
configuration problem?
Thanks
Justin
The following bug has been logged online:
Bug reference: 3503
Logged by: Justin Hibbits
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: Linux
Description:Benchmark scripts broken
Details:
It appears that the benchmark script src/test
The following bug has been logged online:
Bug reference: 1377
Logged by: Justin Clift
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Various
Description:Testing the bug submission form
Details:
Tom forwarded an email saying the bug
few
seconds to load than I was expecting (about 10 seconds in total), but
didn't time out.
If we get more reports of this, indicating its a continuing problem,
then we'll look into it. Otherwise, hopefully the failure was just a
once-off.
Thanks for letting us know guys.
Regard
Hi all,
Does anyone have further input on this?
Regards and best wishes,
Justin Clift
Justin Clift wrote:
Subject:
[Fwd: Re: misc/72498: Libc timestamp code on jailed SMP machine
generates incorrect results]
From:
Justin
pool" of it as made
available on the host system, but have been under the impression
PostgreSQL is coded to not corrupt in this kind of situation.
Regards and best wishes,
Justin Clift
Original Message
Subject: Re: misc/72498: Libc timestamp code on jailed SMP machine
g
Tom Lane wrote:
I believe there are known problems with BSD kernels sometimes returning
wrong clock readings on SMP machines, so that might be a place to look too.
Thanks Tom.
Just filled out a FreeBSD Bug Report, so we'll see how that goes.
:)
Regards and best wishes,
Justin Clift
re
Hi Yuxia,
Which version of PostgreSQL is this with, and did you compile PostgreSQL
yourself?
Regards and best wishes,
Justin Clift
[EMAIL PROTECTED] wrote:
yuxia ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Install
entire PostgreSQL $PGDATA directory (*with
PostgreSQL not running!*).
That way, if anything does go wrong, you can always copy this backup
into place and um.. try again (but differently of course).
:-)
Regards and best wishes,
Justin Clift
> If this is the way to go, please
> confirm th
rally your question is the sort of thing which you need to ask
on the PostgreSQL "General" mailing list, not via a bug report. You'll
probably still find it more beneficial to subscribe to the "General"
mailing list and see what goes on there.
Regards and best wishes,
J
d best wishes,
Justin Clift
> regards, tom lane
>
> ---(end of broadcast)---
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
---(end of broadcast)---
Hi Nitesh,
You need to tune your PostgreSQL system to more efficiently allocate memory
buffers, etc.
http://techdocs.postgresql.org has pointer and documents on how to do this.
Regards and best wishes,
Justin Clift
On Thursday 28 February 2002 17:25, Nitesh wrote:
> I'm using pos
s there about, and this sounds like it might be the best avenue
for you :
http://www.ca.postgresql.org/users-lounge/index.html
Hoping that helps.
:-)
Regards and best wishes,
Justin Clift
On Friday 22 February 2002 16:44, Peter wrote:
> Justin Clift suggested:
> http://www.ejip.net/
ing the present techdocs system of showing known bugs and fixes, etc.
But it's going to take a few months of effort.
:-)
Regards and best wishes,
Justin Clift
On Friday 22 February 2002 23:17, Andy Marden wrote:
> It would be useful to be able to search a list of known bugs for
> the
Peter wrote:
>
> Justin Clift suggested:
> http://www.ejip.net/faq/postgresql_win_setup_faq.jsp
> I started from scratch following the page and adapting it where it is
> out of date. I reached the stage of starting postmaster and receiving
> the message:
> DEBUG: pq_recvb
Hi Paul,
You might like to try the very good installation guide for PostgreSQL on
Windows at :
http://www.ejip.net/faq/postgresql_win_setup_faq.jsp
Added a link to it from the techdocs.postgresql.org website earlier
today too.
:-)
Regards and best wishes,
Justin Clift
On Thursday 21
Hi Andy,
Thats the reason which techdocs.postgresql.org started for, but since it's
grown to encompass so many things, that section hasn't been updated in ages.
:-(
Perhaps its time to look at a better way of keeping it updated?
:-)
Regards and best wishes,
Justin Clift
On T
the same array-equals
> function as the one for text[].
>
> It's too late to fix this in the standard catalogs for 7.2, but I'll
> make a note for 7.3.
Suitable for 7.2.1?
+ Justin
>
> regards, tom lane
>
> ---(end of b
Hi Thomas,
Thanks for this. Just used CFLAGS='-DUSE_AUSTRALIAN_RULES=1' and it compiled
fine.
:-)
Regards and best wishes,
Justin Clift
On Wed, 14 Nov 2001 18:38, Thomas Lockhart wrote:
> ...
>
> > Is there no way to get this working?
>
> Sure there is. The
Hi Bruce,
There is ZERO possibility of using 7.2betaX on this server. It's a
critical production machine and requirements are such that it's been
migrated to RedHat 7.1.
Is there no way to get this working?
Regards and best wishes,
Justin Clift
Bruce Momjian wrote:
>
> Ple
server has kept the number of packages on this server
to a minimum, so it's possible some needed program is missing.
Does anyone have any ideas? Please bear in mind that everything
compiles fine without the -DUSE_AUSTRALIAN_FLAGS option.
Haven't tried current CVS, but it's an intere
and best wishes,
Justin Clift
--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi
---
installed already about 4 prior versions of PostgreSQL, every time working this
>same way and never had this problem, every time working on some Mandrake distribution.
I strongly feel you already had/have some kind of PostgreSQL
installation on your system, and I would point the finger
Hi Bruce,
Bruce Momjian wrote:
>
> Attached is a patch that changes "sequential" to "ever-increasing".
That's a good idea. :) I was trying to think of the right wording, but
I could only think of sentences that were too complex. That one's nice
and simpl
rner site" which Vince created. Looks
pretty nice, new color scheme, better layout, etc. People get to it
when clicking on "Developer's Corner" from the main PostgreSQL site.
:)
Regards and best wishes,
Justin Clift
>
> reg
Tom Lane wrote:
>
> Justin Clift <[EMAIL PROTECTED]> writes:
> > I would have though that after 00FE would be
> > 0100, not 0001.
>
> > Just checked through the Interactive docs (not sure which version of 7.1
> > t
the numbers should be sequential. Just checked the
archives and didn't find anything regarding this.
Bug or not?
Regards and best wishes,
Justin Clift
--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to tr
her than 32, then
restart PostgreSQL. This value can also be altered at compile time to
whatever you want (32 is the default here and thats what gets passed to
the postgresql.conf file).
Hope this helps.
Regards and best wishes,
Justin Clift
[EMAIL PROTECTED] wrote:
>
> Sergio Muscat ([EMAIL
ger to the postmaster process as
you've suggested and see what it thinks is going on.
:-)
Regards and best wishes,
Justin Clift
Tom Lane wrote:
>
> Justin Clift <[EMAIL PROTECTED]> writes:
> > Just did a :
> > pg_ctl stop -m fast
> > And the postmaster process won&
e.
Regards and best wishes,
Justin Clift
[EMAIL PROTECTED] wrote:
>
> JP ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> debug_level 0 does not stop debug messages
>
> Long Description
>
is was fixed in 7.1.
i.e. '192.168.1.1'
Depending on how you're doing things, you *might* be able to wrap stuff
in a btrim() function for 7.0.x.
i.e. btrim() should return '192.168.1.1'
Well, you get the idea. Might be a start of a workaround for you
anyway.
Regard
Hi Jay,
Which OS are you using? Mandrake-Linux 7.2 is known to have bugs in the
version of PostgreSQL they supply as RPM's.
Regards and best wishes,
Justin Clift
[EMAIL PROTECTED] wrote:
>
> Jay Guerette ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the n
Can you tell me more about this strange behaviour? If it's appropriate,
I'll try to get it onto the techdocs website.
Regards and best wishes,
Justin Clift
Tom Lane wrote:
>
> [EMAIL PROTECTED] writes:
> > We noticed a strange behavior involving 'except' an
That sounds like The Right Way of doing it; most responsible,
technically sound, etc.
Regards and best wishes,
Justin Clift
Larry Rosenman wrote:
> I suspect renaming it would be the best way, since we have 2 major
> (SUN, SCO) vendors claiming a des_encrypt() function in their li
ng this now to
their developer list) and also work around the problem ourselves?
Regards and best wishes,
+ Justin Clift
Peter Eisentraut wrote:
>
> Justin Clift writes:
>
> > When --with-openssl= is given to configure
> > on Solaris 8 INTEL, the compilation errors in :
>
them know that something may be wrong?
They're up to beta2 of their next release so now's probably the time to
work things out.
Regards and best wishes,
Justin Clift
Tom Lane wrote:
>
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Justin Clift writes:
>
ange the amount of shared memory segments and
semaphores.
Whenever I have those problems, I insert the updated (higher) values for
shared memory and semaphores, reboot the system, then the tests pass as
the backend is able to start fine.
Hope this is helpful.
Regards and best wishes,
Justin Clift
array
isbn_issn lo mSQL-interface mac miscutil noupdate oid2name pg_dumplo
pg_logger pgbench pgcrypto rserv seg soundex spi string tips unixdate
userlock vacuumlo; do \
if [ -e $dir/Makefile ]; then \
make -C $dir clean; \
fi; \
done
/bin/sh: test: argument expected
make[1]:
Hi all,
There's a spelling mistake on the users-lounge part of the PostgreSQL
website...
"pgsql-bugs If you find bug, fill "
should be :
"pgsql-bugs If you find a bug, fill "
Yes, it's small. But's it's kind of funny
Sorry, forgot to put the -request on the end of the username in the
email address.
+ Justin Clift
Sorry,
I somehow missed including the exact error message I get when inserting
:
Bad (null) varchar() external representation
Regards and best wishes,
Justin Clift
Database Administrator
[EMAIL PROTECTED] wrote:
>
> Justin Clift ([EMAIL PROTECTED]) reports a bug with a severity of 2
51 matches
Mail list logo
