-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Monday, May 26, 2014 5:35 PM
To: Alban Hertroys
Cc: Khangelani Gama; Thomas Kellerer; pgsql-general@postgresql.org
Subject: Re: [GENERAL] postgreSQL : duplicate DB names
Alban Hertroys writes:
> On 26 May 2014, at 10:28,
> The discussions at PGCon pointed out that with the posting-list
compression logic added in 9.4, GIN indexes are pretty close to this
already. Multiple items on the same heap page will typically only take one
byte of index space per item; but there is an identifiable entry, so you
don't get into
Rushi wrote
> copy (select * from (select s1.head as h1,s1.tail as t1 ,s2.tail as
> neighbor from miami_2d s1, miami_directednetwork s2 where s1.tail=s2.head
> and s2.tail not in (select tail from miami_2d where head=s1.head)) as O
> where O.h1!=O.neighbor) to '/tmp/tmp.txt'
Some thoughts:
The O
Alban Hertroys writes:
> On 26 May 2014, at 10:28, Khangelani Gama wrote:
>> It's psql 8.0.4, OS is Red Hat Linux release 9 (Shrike
> 8.0.4? That went EOL almost 4 years ago and even then you should be running a
> version around 8.0.26. Youre 22 bugfix releases behind, which likely
> includes
-Original Message-
From: Alban Hertroys [mailto:haram...@gmail.com]
Sent: Monday, May 26, 2014 11:11 AM
To: Khangelani Gama
Cc: Thomas Kellerer; pgsql-general@postgresql.org
Subject: Re: [GENERAL] postgreSQL : duplicate DB names
On 26 May 2014, at 10:28, Khangelani Gama wrote:
> On 26 Ma
On 26 May 2014, at 10:28, Khangelani Gama wrote:
> On 26 May 2014, at 10:09, Khangelani Gama wrote:
>>> Khangelani Gama, 26.05.2014 09:20:
Hi
Something wrong happened in our server, for some strange and unknown
reason (s) the server created another DB, there is two same DB n
-Original Message-
From: Alban Hertroys [mailto:haram...@gmail.com]
Sent: Monday, May 26, 2014 10:21 AM
To: Khangelani Gama
Cc: Thomas Kellerer; pgsql-general@postgresql.org
Subject: Re: [GENERAL] postgreSQL : duplicate DB names
On 26 May 2014, at 10:09, Khangelani Gama wrote:
>> Khangela
On 26 May 2014, at 10:09, Khangelani Gama wrote:
>> Khangelani Gama, 26.05.2014 09:20:
>>> Hi
>>>
>>> Something wrong happened in our server, for some strange and unknown
>>> reason (s) the server created another DB, there is two same DB names in
>>> one server.
>>>
>>> Name| Owner | Enco
Hi,
I get:
name
--
"a9004"
"template1"
"template0"
"a9004"
(4 rows)
-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Thomas Kellerer
Sent: Monday, May 26, 2014 9:42 AM
To: pgsql-general@postgresql.or
Khangelani Gama, 26.05.2014 09:20:
> Hi
>
> Something wrong happened in our server, for some strange and unknown reason
> (s) the server created another DB,
> there is two same DB names in one server.
>
> Name| Owner | Encoding
> -+--+--
> a9004| postgres |
Hi,
On 2014-05-25 12:26:20 -0700, Maciek Sakrejda wrote:
> I've been trying to take the 9.4 beta for a spin, but seem to have run into
> a shared memory issue on startup:
>
> FATAL: could not open shared memory segment "/PostgreSQL.1804289383":
> Permission denied
>
> We're running Postgres insi
Hi
Something wrong happened in our server, for some strange and unknown reason
(s) the server created another DB, there is two same DB names in one
server. How I can I fix this. Please help
Name| Owner | Encoding
+--+--
a9004| postgres | UNICODE
12 matches
Mail list logo
