On 02/22/2015 11:02 PM, VENKTESH GUTTEDAR wrote:
Hello,
i have Postgresql 9.3.5 installed and django 1.7 and till now it
was working fine.
But now i am getting the following error while starting the server
to run my app :
Unhandled exception in thread started by .wrapper at 0xb2da80
Samuel Smith schrieb am 23.02.2015 um 05:21:
> I am stuck with redhat as the OS so I'll only have initdb. But this is a good
> point.
> I assume there is nothing wrong with having multiple postgres instances
> (clusters) all running under a
> single postgres user on different ports on the same
Hello,
i have Postgresql 9.3.5 installed and django 1.7 and till now it was
working fine.
But now i am getting the following error while starting the server to
run my app :
Unhandled exception in thread started by .wrapper at 0xb2da8074>
Traceback (most recent call last):
File
"/usr/l
On Feb 23, 2015 5:29 AM, "Samuel Smith" wrote:
>
> On 02/22/2015 01:53 PM, Scott Marlowe wrote:>
> > I'd run a debian based distro (Ubuntu or Debian work well) and use the
> > pg_* commands to create the clusters the same way. Gives you the
> > maximum separation for clients.
> >
> > pg_createclus
On 23/02/15 17:21, Samuel Smith wrote:
On 02/22/2015 01:53 PM, Scott Marlowe wrote:>
> I'd run a debian based distro (Ubuntu or Debian work well) and use the
> pg_* commands to create the clusters the same way. Gives you the
> maximum separation for clients.
>
> pg_createcluster
>
> Usage: /usr/b
On 02/22/2015 01:53 PM, Scott Marlowe wrote:>
> I'd run a debian based distro (Ubuntu or Debian work well) and use the
> pg_* commands to create the clusters the same way. Gives you the
> maximum separation for clients.
>
> pg_createcluster
>
> Usage: /usr/bin/pg_createcluster [options]
> [-- ]
On 23/02/15 15:53, Samuel Smith wrote:
On 02/21/2015 05:25 PM, David Steele wrote:
On 2/21/15 6:08 PM, Adrian Klaver wrote:
Currently the built in replication solutions work at the cluster level,
not at the database level. There are third party tools, Slony and
Bucardo come to mind, that can w
On 02/21/2015 05:25 PM, David Steele wrote:
On 2/21/15 6:08 PM, Adrian Klaver wrote:
Currently the built in replication solutions work at the cluster level,
not at the database level. There are third party tools, Slony and
Bucardo come to mind, that can work at a more focused level.
Again, it
Hi,
I'm trying to use a composite type in a WHERE clause, as described here:
http://www.postgresql.org/docs/9.4/static/rowtypes.html
Just pasting in the examples I get:
CREATE TYPE complex AS (
r double precision,
i double precision
);
CREATE TYPE inventory_item AS (
na
Hi,
I'm trying to use a composite type in a WHERE clause, as described here:
http://www.postgresql.org/docs/9.4/static/rowtypes.html
Just pasting in the examples I get:
CREATE TYPE complex AS (
r double precision,
i double precision
);
CREATE TYPE inventory_item AS (
na
On Sun, Feb 22, 2015 at 11:42 AM, Adrian Klaver
wrote:
>
> test=> select * from on_hand where item = '("fuzzy
> dice",42,1.99)'::inventory_item;
>
> item | count
> +---
> ("fuzzy dice",42,1.99) | 1000
> (1 row)
>
So, you have to do the explicit c
On Sun, Feb 22, 2015 at 12:56 PM, Tom Lane wrote:
> Well, it's an unimplemented feature anyway. I poked into it and noticed
> that the equivalent case for arrays works, because that operator is
> "anyarray = anyarray". enforce_generic_type_consistency() observes that
> we have an unknown litera
Eric Hanson writes:
> On Sun, Feb 22, 2015 at 11:47 AM, Tom Lane wrote:
>> Now, I'm not too sure *why* it's making you do that --- seems like the
>> default assumption ought to be that the literal is the same type as
>> the variable it's being compared to. Perhaps there's a bug in there,
>> or p
On Sun, Feb 22, 2015 at 12:18:21PM -0800, Eric Hanson wrote:
> Got it. Ok, I'm reporting this as a bug. Is this a bug? Being able to
> always express literals as text is a really valuable assumption to be able
> to rely on.
If I had to guess (I guess someone more authoritative than I will
chime
On Sun, Feb 22, 2015 at 11:47 AM, Tom Lane wrote:
> Eric Hanson writes:
> > How do I express a composite type literal as text?
>
> The rules are given in the manual ...
>
> > I can't use the ROW() notation, because all values need to be represented
> > as text over a REST api. But I can't seem
On Sun, Feb 22, 2015 at 11:42 AM, Adrian Klaver
wrote:
>
> test=> select * from on_hand where item = '("fuzzy
> dice",42,1.99)'::inventory_item;
>
> item | count
> +---
> ("fuzzy dice",42,1.99) | 1000
> (1 row)
>
So, you have to do the explicit c
"Daniel Verite" writes:
> Giuseppe Sacco wrote:
>> Another important fact is about large objects, if you happen to use
>> them: their OID is not just unique to the database, but to the whole
>> cluster. This means that when you move a database in a cluster from a
>> production system to a da
On Sat, Feb 21, 2015 at 3:01 PM, Samuel Smith wrote:
> Howdy,
> I am looking for advice on migrating to postgres from another database
> system.
>
> Without going into too much detail, my company offers a software solution
> which we self host ourselves in our data center. We have gotten a green
>
Eric Hanson writes:
> How do I express a composite type literal as text?
The rules are given in the manual ...
> I can't use the ROW() notation, because all values need to be represented
> as text over a REST api. But I can't seem to get the text-based syntax to
> work:
> select * from on_hand
On 02/22/2015 10:07 AM, Eric Hanson wrote:
> Hi,
>
> How do I express a composite type literal as text?
>
> I'm trying to use a composite type in a WHERE clause. The examples in
> the docs
>
> http://www.postgresql.org/docs/9.4/static/rowtypes.html
>
> say:
>
> CREATE TYPE complex AS (
>
Giuseppe Sacco wrote:
> Another important fact is about large objects, if you happen to use
> them: their OID is not just unique to the database, but to the whole
> cluster. This means that when you move a database in a cluster from a
> production system to a database on a test cluster, yo
Hi,
How do I express a composite type literal as text?
I'm trying to use a composite type in a WHERE clause. The examples in the
docs
http://www.postgresql.org/docs/9.4/static/rowtypes.html
say:
CREATE TYPE complex AS (
r double precision,
i double precision
);
CREATE TYP
Hi,
There is no 2nd server involved. The pg_dump runs on the server where postgres
server is running. The regular dump runs the same way and it completes
Successfully within 3 hours. It’s only parallel dump fails on the table with
size about 48GB. We run the pg_dump through an script on the postg
2015-02-20 14:26 GMT-08:00 Shanker Singh :
> I tried turning off ssl renegotiation by setting "ssl_renegotiation_limit
> = 0" in postgresql.conf but it had no effect. The parallel dump still fails
> on large tables consistently.
>
> Thanks
> Shanker
>
>
HI,
Maybe you could try to setup an SSH con
>Howdy,
>I am looking for advice on migrating to postgres from another database
>system.
>
>Without going into too much detail, my company offers a software
>solution which we self host ourselves in our data center. We have gotten
>a green light from management to start using postgres as a free an
Il giorno sab, 21/02/2015 alle 16.01 -0600, Samuel Smith ha scritto:
> Howdy,
> I am looking for advice on migrating to postgres from another database
> system.
[...]
People already wrote you some comments, here are two more.
DB2 instances run as different OS users, so if you need the same
appro
26 matches
Mail list logo
