Hello,
I tried the following scenario on PostgreSQL 9.4.2 on Linux:
1) Connect to a remote postgres database and run a long running query
e.g. psql -h vm5 -p 57001 warehouse -c 'select x.a from
generate_series(1, 1) as x(a);'
2) Suspend the client process by pressing CTRL-Z
3) In anothe
Le 2013-04-18 à 16:02, Tom Lane a écrit :
> =?iso-8859-1?Q?Fran=E7ois_Beausoleil?= writes:
>> I received the following error while backing up my database:
>
>> pg_dump: Dumping the contents of table
>> "summary_show_unique_personas_2012_10_15" failed: PQgetCopyData() failed.
>> pg_dump: Error
I'd say you either have overloaded application (try increasing timeout),
too small pool (increase pool) or connection leaks (find and fix).
18 квіт. 2013 23:45, "itishree sukla" напис.
> Dear All,
>
> Can any one please help me to fix this issue, i am getting this error from
> our application, cu
=?iso-8859-1?Q?Fran=E7ois_Beausoleil?= writes:
> I received the following error while backing up my database:
> pg_dump: Dumping the contents of table
> "summary_show_unique_personas_2012_10_15" failed: PQgetCopyData() failed.
> pg_dump: Error message from server: pg_dump: The command was: COPY
On 04/18/2013 01:08 PM, Eduardo Morras wrote:
> On Thu, 18 Apr 2013 20:35:37 +1000
> Chris Angelico wrote:
>
>> That one's clearly fine. What about www.postgresql.org? It's possible
>> you have a poisoned cache for just that one record.
>>
>> ChrisA
>
> I have clean all (dns, web cache, etc) and
Hello list,
I received the following error while backing up my database:
pg_dump: Dumping the contents of table
"summary_show_unique_personas_2012_10_15" failed: PQgetCopyData() failed.
pg_dump: Error message from server: pg_dump: The command was: COPY
public.summary_show_unique_personas_2012_1
Not really sure of your exact situation, if your network is really flaky
you really need to fix that and if your trying to do streaming over a
WAN, you might be better off doing log shipping instead.
But what we do here with one live and one hot-standby via streaming is
synchronous_commit = of
Hi
Sincerely, if you are missing tcp packets you first should recheck the
environment because this issue is not acceptable in any cases, but less if we
are talking about HA databases.
If you are cofiguring this with remote machines or similar, try to use async
and pgwall recovery system.
If
Hi,
I am using Postgres DB with stand by database, configured with streaming in
synchronized mode (each commit on primary DB waits for commit on secondary DB).
Sometimes we suffer from network issues and as consequences, secondary machine
is not available.
In these situations, our application
> Why you just create your track function and a view to call it?
>
> Example:
>
> BEGIN;
>
> CREATE TABLE foo (id SERIAL PRIMARY KEY, data TEXT);
> CREATE TABLE foo_track(tracktime TIMESTAMP DEFAULT now(), foo_row foo);
>
> INSERT INTO foo (data) SELECT 'Some Data'||id FROM generate_series(1,10) AS
On Thu, Apr 18, 2013 at 11:02 AM, Atri Sharma wrote:
>
> [...]
>
> One way I was thinking of was creating an updatable view, which is
> initialized to NULL. As SELECT queries take place, I can update the
> view to include the new rows.
>
>
Why you just create your track function and a view to cal
On 04/18/2013 07:19 AM, Atri Sharma wrote:
So what would you run the SELECT against, another view or table?
No, what I meant was:
SELECT on main table: fires a rule which updates a view V1
Now, essentially, view V1 has the data I was trying to acquire
originally through BEFORE INSERT trigger
>
> So what would you run the SELECT against, another view or table?
No, what I meant was:
SELECT on main table: fires a rule which updates a view V1
Now, essentially, view V1 has the data I was trying to acquire
originally through BEFORE INSERT trigger.
When I need the data, I can query view V
On 04/18/2013 07:02 AM, Atri Sharma wrote:
How about a RULE:
http://www.postgresql.org/docs/9.2/interactive/sql-createrule.html
Rules can be tricky, so I would at least skim through:
http://www.postgresql.org/docs/9.2/interactive/rules.html
Thanks.
It looks like that it is another way to cr
> How about a RULE:
>
> http://www.postgresql.org/docs/9.2/interactive/sql-createrule.html
>
> Rules can be tricky, so I would at least skim through:
>
> http://www.postgresql.org/docs/9.2/interactive/rules.html
Thanks.
It looks like that it is another way to create a view, which is
probably not
Hi John,
On 17 Apr 2013, at 11:30 AM, John R Pierce wrote:
> on AIX, I build mine to run in /opt/$MYGROUP/pgsql/9.2 and I just tar it up
> and distribute it as a tarball to my operations people. I'd previously asked
> them if they wanted it as a system package, and their response was 'why
> bo
On 04/18/2013 05:12 AM, Atri Sharma wrote:
On Thu, Apr 18, 2013 at 5:35 PM, Alfonso Afonso wrote:
Hi Atri
Maybe you could think different and, instead of do a "before select trigger",
you can:
- create a store procedure with result is a recordset
- create a view
If you can't... could you pl
On Thu, Apr 18, 2013 at 5:35 PM, Alfonso Afonso wrote:
> Hi Atri
>
> Maybe you could think different and, instead of do a "before select trigger",
> you can:
>
> - create a store procedure with result is a recordset
> - create a view
>
> If you can't... could you please explain us a bit more abou
Hi Atri
Maybe you could think different and, instead of do a "before select trigger",
you can:
- create a store procedure with result is a recordset
- create a view
If you can't... could you please explain us a bit more about the requirements
about this before action?
Good luck
Regards
El
Eduardo Morras wrote:
> In 87.238.57.232 (Sweeden) 98.129.198.126(San Antonio,TX) and
> 217.196.149.50(Saltzburg) i get lighttpd default page.
>
> Perhaps a miss configuration on my ISPs dns.
These IP addresses look fine, but it's not unexpected that using them
directly in the browser's
On Thu, 18 Apr 2013 20:35:37 +1000
Chris Angelico wrote:
> That one's clearly fine. What about www.postgresql.org? It's possible
> you have a poisoned cache for just that one record.
>
> ChrisA
I have clean all (dns, web cache, etc) and get:
camibar% nslookup www.postgresql.org
Server:
On Thu, Apr 18, 2013 at 8:32 PM, Eduardo Morrás wrote:
> On Thu, 18 Apr 2013 18:40:40 +1000
> Chris Angelico wrote:
>
>> Works for me. Do a name lookup - what IP address do you get? I get:
>>
>> postgresql.org. 17973 IN A 217.196.149.50
>>
>> www.postgresql.org. 269 I
On Thu, 18 Apr 2013 18:40:40 +1000
Chris Angelico wrote:
> On Thu, Apr 18, 2013 at 6:33 PM, Magnus Hagander wrote:
> > On Thu, Apr 18, 2013 at 10:31 AM, Eduardo Morras wrote:
> >>
> >>
> >> I get Godaddy's page saying it's free
> >
> > Really?
> >
> > Whois shows it expires Oct 21 - and surely
On Thu, Apr 18, 2013 at 10:37 AM, Eduardo Morras wrote:
> On Thu, 18 Apr 2013 10:33:20 +0200
> Magnus Hagander wrote:
>
>> On Thu, Apr 18, 2013 at 10:31 AM, Eduardo Morras wrote:
>> >
>> >
>> > I get Godaddy's page saying it's free
>>
>> Really?
>>
>> Whois shows it expires Oct 21 - and surely i
On Thu, Apr 18, 2013 at 6:33 PM, Magnus Hagander wrote:
> On Thu, Apr 18, 2013 at 10:31 AM, Eduardo Morras wrote:
>>
>>
>> I get Godaddy's page saying it's free
>
> Really?
>
> Whois shows it expires Oct 21 - and surely it will be renewed by then.
> and godaddy says it's registered (though no det
On Thu, Apr 18, 2013 at 10:31 AM, Eduardo Morras wrote:
>
>
> I get Godaddy's page saying it's free
Really?
Whois shows it expires Oct 21 - and surely it will be renewed by then.
and godaddy says it's registered (though no details).
Any chance you just spelled it wrong?
--
Magnus Hagander
M
I get Godaddy's page saying it's free
--- ---
Eduardo Morras
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Hi all,
I need a tool which allows me to do a task before every SELECT on a
table. Specifically,the behavior I would get with a BEFORE SELECT
trigger.
Please advice me on this.
Regards,
Atri
--
Regards,
Atri
l'apprenant
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
28 matches
Mail list logo
