> -Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Sent: Wednesday, March 5, 2014 9:17 PM
> To: Raschick, Hartmut
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] too-may-open-files log file entries when
> vauuming under solaris
>
> "Raschick, Hartmut" writes:
I recommend Vertabelo - http://www.vertabelo.com. It’s an online
database designer working under Chrome. It is free to use for smaller
projects and have commercial version for larger.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
htt
One point - a serial datatype will not increment to infinity, as it is
effectively a 4 byte integer with a sequence imposed, it can only store values
upto MAXINT (2147483647) . Above this it may well wrap around where MAXINT + 1
= 1
You can delay the problem (significantly) by using bigserial (
Bingo, this COPY file did not have the datetimeval, so I added a few lines
of code to convert it from the ctime-type entry that exists in the record.
You would think that postgres could have output a more helpful error
message, though.
Thanks a lot for the assist.
Susan
On Fri, Mar 7, 2014 at 3
On 03/07/2014 03:10 PM, Israel Brewster wrote:
/usr/local/pgsql/bin/pg_dump -h -U tracking -cs |
/usr/local/pgsql/bin/psql -U postgres tracking
It must have been left over from before I got streaming replication up and
working, when this box was still the backup server and not primary -i.e.
On 03/07/2014 04:06 PM, Adrian Klaver wrote:
On 03/07/2014 02:48 PM, Susan Cassidy wrote:
I have another problem with a slightly different trigger. It's very
weird, because it is exactly the same as the first trigger, that now
works, except for the table name.
The error is:
ERROR: query stri
---
Israel Brewster
Computer Support Technician II
Era Alaska
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x7293
---
BEGIN:VCARD
VERSION:3.0
N:Brewster;Israel;;;
FN:Israel Brewster
ORG:Frontie
On 03/07/2014 02:48 PM, Susan Cassidy wrote:
I have another problem with a slightly different trigger. It's very
weird, because it is exactly the same as the first trigger, that now
works, except for the table name.
The error is:
ERROR: query string argument of EXECUTE is null
CONTEXT: PL/pg
I have another problem with a slightly different trigger. It's very weird,
because it is exactly the same as the first trigger, that now works, except
for the table name.
The error is:
ERROR: query string argument of EXECUTE is null
CONTEXT: PL/pgSQL function metric_int_insert_func() line 5 at
On 03/07/2014 11:08 AM, Israel Brewster wrote:
On Mar 6, 2014, at 1:25 PM, Steve Crawford
wrote:
On 03/06/2014 09:33 AM, Israel Brewster wrote:
For starters, this happened again this morning (no data prior to 4:45 am and
sequence reset), so whatever is going on appears to be reoccurring. Al
Hey guys,
This will be the first, and hopefully not last, PostgreSQL-related tool my
company has allowed me to Open Source. The shard_manager extension offers a lot
of helper functions and a system for managing fully unique IDs across many
database shards. You can find it on our github page:
h
On Mar 6, 2014, at 1:25 PM, Steve Crawford
wrote:
> On 03/06/2014 09:33 AM, Israel Brewster wrote:
>> For starters, this happened again this morning (no data prior to 4:45 am and
>> sequence reset), so whatever is going on appears to be reoccurring. Also, I
>> forgot to mention if it is signif
So the logs have given me a partial answer, specifically WHO and WHAT. I still
have to track down WHY:
[unknown]-2014-03-07 04:40:02.407 AKST-0LOG: connection received: host=[local]
postgres-2014-03-07 04:40:02.409 AKST-0LOG: connection authorized:
user=postgres database=tracking
postgres-2014
Catherine Devlin writes:
> I just looked into describe.c, but it was virtually my first look at C
> in 15 years and I'm pretty intimidated.
It's ugly and messy even to someone who does C every day, so don't feel bad.
> Come to think of it, I really like the idea of moving the query
> execution a
Hello
2014-03-07 16:42 GMT+01:00 Catherine Devlin :
> On Thu, Mar 6, 2014 at 12:09 PM, Tom Lane wrote:
> > Hm ... the code in psql's describe.c is not terribly conducive to that.
> > Parsing of the backslash command, execution of the query/queries, and
> > presentation of the results is all r
On Thu, Mar 6, 2014 at 12:09 PM, Tom Lane wrote:
> Hm ... the code in psql's describe.c is not terribly conducive to that.
> Parsing of the backslash command, execution of the query/queries, and
> presentation of the results is all rather tightly bound up; you'd have
> to think about how to decoup
Michael Paquier wrote
> On Fri, Mar 7, 2014 at 3:32 PM, leo <
> dazhoufei@
> > wrote:
>>I just complete my HA configuration on Redhat 6.4 enterprise:
>> Clusterware: Pacemaker 1.1.8 ( CMAN .0.12.1, corosync 1.4.1 )
>> Resource manager: PCS 0.9.26
>> PostgreSQL 9.3.3.1
On Fri, Mar 7, 2014 at 3:32 PM, leo wrote:
>I just complete my HA configuration on Redhat 6.4 enterprise:
> Clusterware: Pacemaker 1.1.8 ( CMAN .0.12.1, corosync 1.4.1 )
> Resource manager: PCS 0.9.26
> PostgreSQL 9.3.3.1
> Detailed configuration follow:
> http://clu
18 matches
Mail list logo
