The following bug has been logged on the website:
Bug reference: 6532
Logged by: Stuart Bishop
Email address: stu...@stuartbishop.net
PostgreSQL version: 9.1.3
Operating system: Ubuntu
Description:
The 9.1.3 changelog states pg_upgrade's handing of plpython s
The following bug has been logged on the website:
Bug reference: 6624
Logged by: Stuart Bishop
Email address: stu...@stuartbishop.net
PostgreSQL version: 9.1.3
Operating system: Ununtu
Description:
psql tab completion can emit WARNING messages if
The following bug has been logged on the website:
Bug reference: 7546
Logged by: Stuart Bishop
Email address: stu...@stuartbishop.net
PostgreSQL version: 9.1.5
Operating system: Ubuntu 12.10
Description:
I have a primary and a hot standby using streaming replication
The following bug has been logged on the website:
Bug reference: 7661
Logged by: Stuart Bishop
Email address: stu...@stuartbishop.net
PostgreSQL version: 9.1.6
Operating system: Ubuntu 12.04
Description:
The pgstattuple upgrade from unpackaged script expects the
The following bug has been logged on the website:
Bug reference: 8450
Logged by: Stuart Bishop
Email address: stu...@stuartbishop.net
PostgreSQL version: 9.1.9
Operating system: all
Description:
Hi.
pg_basebackup blocks until all necessary WAL files have been
The following bug has been logged online:
Bug reference: 4539
Logged by: Stuart Green
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.11
Operating system: Centos 5
Description:to_char(to_timestamp('...','')) returns the wrong
result
title from bug where title !~* '[ae]';
Lists all titles that don't contain a, q, x or z: WORKS
[4] select title from bug where title ~* '^[^ae]';
Lists all titles that do not begin with a, q, x or z: WORKS
I hope this helps with development,
Regards,
Stuar
rashme.sql
I've only tried reproducing this with latest released Ubuntu packages
(Feisty) for 8.2.5.
Also reported in the Ubuntu bug tracker too:
https://bugs.launchpad.net/ubuntu/+source/postgresql/+bug/144740
--
Stuart Bishop <[EMAIL PROTECTED]>
http://www.stuartbishop.net/
sign
tested with PG 8.2.5 under Ubuntu Feisty so far, although
we found the original problem under 8.2.4 on Ubuntu Dapper.
Also reported in the Ubuntu bug tracker at:
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.2/+bug/146382
--
Stuart Bishop <[EMAIL PROTECTED]>
http://www.stuartbishop.n
--
2002-11-26 13:47:34.88358+00
(1 row)
testdb2=# select timestamp 'now';
timestamptz
---
2002-11-26 13:47:47.701731+00
(1 row)
The first SELECT returns a 'timestamp', but the next two return a
'timestamptz'
The following bug has been logged online:
Bug reference: 5857
Logged by: Stuart Bishop
Email address: stu...@stuartbishop.net
PostgreSQL version: 8.4.6
Operating system: Ubuntu 10.10
Description:pg_restore --clean dropping type too soon
Details:
"pg_restore --
The following bug has been logged on the website:
Bug reference: 6528
Logged by: Stuart Bishop
Email address: stuart.bis...@canonical.com
PostgreSQL version: 9.1.3
Operating system: Ubuntu
Description:
In section 24.3.5.1 of the docs on setting up continuous
o from 8.4. createlang installs
the language just fine if I build a cluster and database myself.
--
Stuart Bishop
http://www.stuartbishop.net/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Thu, Mar 15, 2012 at 9:01 PM, Stuart Bishop wrote:
> Yes, it is there. I can see the library with the new name of
> plpython2.so, not the old plpython.so from 8.4. createlang installs
> the language just fine if I build a cluster and database myself.
As expected, symlinking plpyth
if I should bother reporting
the issue, except for the chance that this bug might have deeper
impact I hadn't thought of.
--
Stuart Bishop
http://www.stuartbishop.net/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
=on, primary_conninfo=...,
recovery_target_timeline=latest)
- The hot standby was started.
Unfortunately I didn't have the disk space around to keep everything,
and am attempting the rebuild again now.
--
Stuart Bishop
http://www.stuartbishop.net/
--
Sent via pgsql-b
On Wed, Aug 29, 2012 at 10:59 PM, Andres Freund wrote:
> On Wednesday, August 29, 2012 05:32:31 PM Stuart Bishop wrote:
>> I believe I just hit this same issue, but with PG 9.1.3:
>>
>> <@:32407> 2012-08-29 10:02:09 UTC LOG: shutting down
>> <@:32407>
On Wed, Sep 19, 2012 at 5:45 AM, Fujii Masao wrote:
> On Mon, Sep 17, 2012 at 7:28 PM, wrote:
>> The following bug has been logged on the website:
>>
>> Bug reference: 7546
>> Logged by: Stuart Bishop
>> Email address: stu...@stuartbishop
primary during the backup window. I can't discount other commands
either, but if that is the case one of our ops needs a spanking. I've
only been able to reproduce the buffer pin error in isolation.
--
Stuart Bishop
http://www.stuartbishop.net/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
st have occurred and can see no DDL
except for the creation and dropping of temporary tables. My parser is
unfortunately grep and my eyeballs to filter out the noise.
--
Stuart Bishop
http://www.stuartbishop.net/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
ry might have needed to see row versions that must be removed.
As before, the only error I've been able to reproduce in isolation is
the buffer pin error I originally reported.
--
Stuart Bishop
http://www.stuartbishop.net/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
. umm... bugtracker, as so far
'FROM unpackaged' has failed in 66% of up updates. Is the real
solution is for the foo--unpackaged--1.0.sql script to recreate
missing objects before adding them to the extension?
--
Stuart Bishop
http://www.stuartbishop.net/
--
Sent via pgsql-bugs ma
nction value.
I think this is the same issue as was discussed here, dating from
PostgreSQL 8.1:
http://postgresql.1045698.n5.nabble.com/Slow-functional-indexes-td2059587.html
--
Stuart Bishop
http://www.stuartbishop.net/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To mak
ommand is failing.
I'm supporting PG 9.1 at the moment so cannot rely on
--xlog-method=stream. I agree that the current behavior is for most
use cases better, and I think that the behavior I want should be
explicitly enabled with an option.
--
Stuart Bishop
http://www.stuartbishop.net/
4/msg00060.html
If this is indeed to remain the case I think it should be clearly documented
in the rules section (I guess it would affect all defaults that use
functions).
Any way heres my script and stuff:
<> <>
- Stuart
tbl_ins_test.sct
ins_rule_test.sql
l'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/postgresql-7.1beta6/src'
make: *** [all] Error 2
Full configure output:
<>
Full Make Output:
<>
-Stuart
[Side FYI:
I had an error with the bug reporting tool:
1: Gave a to large code example (over 8140 - u
SEVERITY:Minor Anoyance
In the plpgsql docs it has the following example:
RAISE NOTICE ''Id number '' || key || '' not found!'';
When I put a function round this statement it gives a compile error at the
|.
Also when fiddling if I put a variable first it complains about that
variable (eg key || '
cords with Primary keys
based upon the sequence where present in the table. (I *think* it was a
different table & sequence last time).
- Stuart
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
No. I had fsync on.
- Stuart
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]]
Sent: 19 December 2001 18:49
To: Mikheev, Vadim
Cc: Henshall, Stuart - WCP; [EMAIL PROTECTED]
Subject: Re: [BUGS] After ~Crash Sequence not correct
"Mikheev, Vadim" <[EMAIL PROTE
There was a cygwin postgresql 7.1.3-2 release to fix a file handle problem
(init_rels() not closing pg_internal.init):
http://archives.postgresql.org/pgsql-cygwin/2002-01/msg00034.php
which refers to:
http://archives.postgresql.org/pgsql-cygwin/2002-01/msg00029.php
Maybe this is it?
- Stuart
check
All tests PASSED
./configure --enable-thread-safety --with-pam --with-java --with-openssl
make
make check
All tests PASSED
We use Postgresql daily, we store a database of over 12 million rows and
everything hums along nicely. Keep up the good work.
--
Stuart Stock
Dresdner Kleinwort
on();
version
--
PostgreSQL 7.2.3 on i686-pc-cygwin, compiled by GCC 2.95.3-5
(1 row)
Thank you,
- Stuart
nal representation 'Thu Nov 28 11:26:46.488000 2002 G
MTST'
dev=# select timeofday();
timeofday
---
Thu Nov 28 11:26:59.454000 2002 GMTST
(1 row)
- Stuart
Title: RE: [BUGS] timeofday()::timestamp - not casting
Tom Lane wrote:
> "Henshall, Stuart - Design & Print"
> <[EMAIL PROTECTED]> writes:
>> dev=# select timeofday()::timestamp;
>> ERROR: Bad timestamp external representation 'Thu Nov 28
>>
34 matches
Mail list logo
