On Sun, May 22, 2016 at 9:10 AM, Adrian Klaver
wrote:
> On 05/22/2016 09:06 AM, Tory M Blue wrote:
>>
>>
>>
>>
>>> On May 22, 2016, at 07:50, Adrian Klaver
>>> wrote:
>>>
>
>>>
>>> So where did you get the 'stock&#x
> On May 22, 2016, at 07:50, Adrian Klaver wrote:
>
>> On 05/21/2016 10:27 PM, Tory M Blue wrote:
>> Evening, morning, or afternoon,
>>
>> So I'm trying to go back to a stock rpm package (vs my full custom,
>> builds). This is a learning curve, not
Evening, morning, or afternoon,
So I'm trying to go back to a stock rpm package (vs my full custom,
builds). This is a learning curve, not only because it's all "whacked
pathing (in my eyes:)) but rhel7 is a #$%$# with all the things they
changed.
Sooo
I've got servers built and I've got the co
On Tue, Apr 19, 2016 at 2:30 PM, John R Pierce wrote:
> On 4/19/2016 2:28 PM, Bill Ross wrote:
>>
>> I've been running an index build for almost an hour on my 30G server that
>> takes ~ 20 mins on my puny old macbook.
>>
>> It seems like I've tuned all I can.. what am I missing?
>
>
>
>
> maintena
Sorry I think I posted this to the wrong group, sent to performance vs
General. My apologies to everyone in perf!
Greetings and salutations.
>
> I've got some weirdness.
>
> Current:
> Postgres 9.3.4
> Slony 2.2.3
> CentOS 6.5
>
> Prior running Postgres 9.1.2 w/slony 2.1.3 CentOS 6.2
>
> I found t
I know you can't do much with this information, but maybe you can help
me acquire the information that is needed.
This started in 8.4 and trying to figure it out
Fedora 12, Postgres 8.4.4 with slony.
Although I don't see any panics or errors other then these Warnings,
but I did see a dead lock t
On Mon, Jul 27, 2009 at 12:51 PM, Phoenix Kiula wrote:
> Just looking for experiences of people. Are people already using 8.4
> in serious live hosting environments? Thanks.
>
Wait..
8.3 is running fine and dandy. Lots of decent sized changes in 8.4
with awaiting fixes. So wait.
And those that
On Tue, Jun 9, 2009 at 11:31 AM, Vyacheslav Kalinin wrote:
>> however the COPY
>> command requires superuser and I really don't want to open up the DB
>> from a remote system with Superuser access.
>
> COPY FROM STDIN does not need superuser privileges.
>
Thanks guys, the problem with copy from or
Good day,
I'm having one heck of a time here. I'm looking for a clean solution
to issue a COPY statement from a remote system. (because I really
don't want to play the ssh, sudo spiel).
It's evident that pg_connect doesn't like the \copy command (it's a no
go), however it is okay with the COPY co
