This issue stays resolved !!!
The statements are no more hanging on production now :)
The suspected problem was -
Our brand new production server did not have the port 5432 open.
I had opened the port using "iptables" command and everything started
working.
synchronous replication is fast and
Le jeudi 09 février 2012 à 16:30 -0600, Merlin Moncure a écrit :
> natural/surrogate is a performance/usability debate with various
> tradeoffs. but using surrogate to 'create' uniqueness is a logical
> design error; maybe a very forgivable one for various reasons, but the
> point stands.
Please
I seem to be able to do full backups, but it doesn't show up in the backups
list when I do a "show" command and the "validate" command doesn't seem to do
anything; doing an incremental backup, it claims the full backup was never
validated, so I can't do increments :-P
I posted on the pg_rman goo
Hello,
Is there a way with psql to get column output to be
"data1","data2",...,"datan"
I tried -F "," but that left off the first and last quote.
I can't seem to find a way in the man page.
Thanks,
--
Stephen Clark
*NetWolves*
Director of Technology
Phone: 813-579-3200
Fax: 813-882-0209
Email:
On Fri, Feb 10, 2012 at 11:26 AM, Steve Clark wrote:
> Hello,
>
> Is there a way with psql to get column output to be
> "data1","data2",...,"datan"
>
> I tried -F "," but that left off the first and last quote.
>
> I can't seem to find a way in the man page.
Well, you can do it yourself kinda lik
On Feb 10, 2012, at 10:49, Vincent Veyron wrote:
> Le jeudi 09 février 2012 à 16:30 -0600, Merlin Moncure a écrit :
>
>> natural/surrogate is a performance/usability debate with various
>> tradeoffs. but using surrogate to 'create' uniqueness is a logical
>> design error; maybe a very forgivabl
On 02/10/2012 02:12 PM, Scott Marlowe wrote:
On Fri, Feb 10, 2012 at 11:26 AM, Steve Clark wrote:
Hello,
Is there a way with psql to get column output to be
"data1","data2",...,"datan"
I tried -F "," but that left off the first and last quote.
I can't seem to find a way in the man page.
Wel
Le vendredi 10 février 2012 à 14:19 -0500, David Johnston a écrit :
> One possibility is to add a "version" field (integer) and combine evenement
> and version to create the unique. I'd also create a partial unique on
> evenement/annule to ensure you do not make more than one active version.
>
The following are the relevant log entries from a recent crash of v9.1.1
running on an older RHEL Linux box. This is the first crash we've
experienced in a lot of years of running Pg. Any assistance in how to
determine what might have caused this is welcome.
--
2012-02-10 13:55:59 CST [15949]:
On Feb 10, 2012, at 14:56, Vincent Veyron wrote:
> Le vendredi 10 février 2012 à 14:19 -0500, David Johnston a écrit :
>
>> One possibility is to add a "version" field (integer) and combine evenement
>> and version to create the unique. I'd also create a partial unique on
>> evenement/annule
On Fri, Feb 10, 2012 at 1:33 PM, Steve Clark wrote:
> On 02/10/2012 02:12 PM, Scott Marlowe wrote:
>
> On Fri, Feb 10, 2012 at 11:26 AM, Steve Clark wrote:
>
> Hello,
>
> Is there a way with psql to get column output to be
> "data1","data2",...,"datan"
>
> I tried -F "," but that left off the fir
On Fri, Feb 10, 2012 at 7:49 AM, Vincent Veyron wrote:
> Le jeudi 09 février 2012 à 16:30 -0600, Merlin Moncure a écrit :
>
> > natural/surrogate is a performance/usability debate with various
> > tradeoffs. but using surrogate to 'create' uniqueness is a logical
> > design error; maybe a very f
On Mon, Dec 12, 2011 at 07:15:12PM +0100, Wim Bertels wrote:
> Hallo,
>
> psql latex output format needs to differentiate between a newline and a
> tabularnewline.
>
> the problem arises when u have a field value that contains a newline
> character, when this field is not the first column, then a
13 matches
Mail list logo
