On 24.05.2011 18:27, manish singh wrote:
When ever i am restarting postgresql slave (Service postgresql restart -
made a script) or even just stopping and starting a postgresql slave.. it
displays a a message, although slave get's started and working fine...
server starting
cp: cannot stat
`/us
On Debian Lenny, I downloaded termcap source from
http://ftp.gnu.org/gnu/termcap/ and installed it. Then the error is gone.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/BUG-5807-psql-fails-to-launch-with-Cannot-read-termcap-database-using-dumb-terminal-settings-Aborted
Robert Haas writes:
> On Sun, May 15, 2011 at 5:02 PM, Tom Lane wrote:
>> Robert Haas writes:
>>> On Thu, May 12, 2011 at 6:20 PM, Tom Lane wrote:
One possibility is to start showing "default" when the ACL is null,
which would be quite easy to implement:
COALESCE(arr
The following bug has been logged online:
Bug reference: 6037
Logged by: manish singh
Email address: delhi.man...@gmail.com
PostgreSQL version: 9.0.3
Operating system: CentOS release 5.3 (Final) - 2.6.18-128.el5xen
Description:error on restarting slave - cp: cannot
"Kevin Grittner" writes:
> You're running into multiple issues here. First off, you should
> understand that "real" is an approximate data type, which is not
> capable of exactly representing many decimal fractions. "numeric"
> can exactly represent decimal fractions. So, while it's OK when you
"jose soares" wrote:
> Description:why a REAL should be queried as a string?
> I'd like to to report this strange behavior, that I think is a
> bug...
>
> # \d frazione
> Table "public.frazione"
>Column | Type | Modifiers
> +-+--
The following bug has been logged online:
Bug reference: 6036
Logged by: jose soares
Email address: jose.soa...@sferacarta.com
PostgreSQL version: 8.4.4
Operating system: x86_64-pc-linux-gnu
Description:why a REAL should be queried as a string?
Details:
I'd like to
In regression testing PostGIS 2.0, our topology module regression tests are
failing in PostgreSQL 9.1 beta.
We have a PostGIS ticket open for it here, but we suspect it's a PostgreSQL
9.1 bug and would like to close it out.
http://trac.osgeo.org/postgis/ticket/980
Our domain type is defined as: