On 12.04.2013 09:41, Singh, Devendra wrote:
Hi All,
I hit a hang issue in postgres 8.4 query. Hit this issue multiple time on
HP-UX. Below is the snapshot of the hang thread.
lwpid : 600943
---
0: c054ced0 : _poll_sys() +
On 4/12/2013 12:10 PM, fburg...@radiantblue.com wrote:
The SQL query should be: select count(*) from dna_strands where cid = 1;
ah. I suspected as much.its so hard to analyze problems with
incorrect information and so easy to make wrong assumptions.
I just realize don't think this is n
Hi John,
The SQL query should be: select count(*) from dna_strands where cid = 1;
I just realize don't think this is not going to work. if for the sake of argument that cid = 1 is much more likely be be found in a more recent partition, any inverse search mechanism in the planner will find tha
On 4/12/2013 11:46 AM, fburg...@radiantblue.com wrote:
We are having performance related problems on one of our big data
Partition tables. The table is partitioned by date and the partitions
are organized from Jan 2003 thru Dec 2013.
We have 268 child partitions associated with the Parent table,
Sorry, Is this visible?
We are having performance related problems on one of our big data Partition tables. The table is partitioned by date and the partitions are organized from Jan 2003 thru Dec 2013. We have 268 child partitions associated with the Parent table, and we have constraint_exclusi
We are having performance related problems on one of our big data Partition tables. The table is partitioned by date and the partitions are organized from Jan 2003 thru Dec 2013. We have 268 child partitions associated with the Parent table, and we have constraint_exclusion=partition set.
The ex
On Fri, Apr 12, 2013 at 7:41 AM, Tom Lane wrote:
> dan...@heroku.com writes:
>> We have a somewhat high-churn table acting as a queue, and over time it's
>> grown to be something like a gigabyte. I surmised it might be vanilla
>> bloat, but the truth seems somewhat more exotic because both VACUUM
On Fri, Apr 12, 2013 at 10:46 AM, Daniel Farina wrote:
> On Fri, Apr 12, 2013 at 7:07 AM, Andres Freund wrote:
>> On 2013-04-12 08:34:24 +, dan...@heroku.com wrote:
>>> The following bug has been logged on the website:
>>>
>>> Bug reference: 8058
>>> Logged by: Daniel Farina
>>>
On Fri, Apr 12, 2013 at 7:07 AM, Andres Freund wrote:
> On 2013-04-12 08:34:24 +, dan...@heroku.com wrote:
>> The following bug has been logged on the website:
>>
>> Bug reference: 8058
>> Logged by: Daniel Farina
>> Email address: dan...@heroku.com
>> PostgreSQL version: 9.
On 2013-04-12 20:02:07 +0300, Tarvi Pillessaar wrote:
> On 12.04.2013 17:04, Andres Freund wrote:
> >On the other hand, at
> >least in the first example you haven't even committed the transaction so
> >there's nothing that could flush the transaction unless we we would
> >*always* flush nextval()
claudio...@hotmail.com writes:
> select count(*) from teste; --- 5000
> select count(*) from teste limit 1000 offset 0; --- 5000
> select count(*) from teste limit 1000 offset 1; --- not returning
Of course. I think perhaps what you are looking for is
select count(*) from (select 1 from
On 12.04.2013 17:04, Andres Freund wrote:
On the other hand, at
least in the first example you haven't even committed the transaction so
there's nothing that could flush the transaction unless we we would
*always* flush nextval() immediately if needs to get new values which
doesn't seem reasonab
Em Sex, 2013-04-12 às 14:57 +, claudio...@hotmail.com escreveu:
> The following bug has been logged on the website:
>
> Bug reference: 8061
> Logged by: Claudio Oliveira
> Email address: claudio...@hotmail.com
> PostgreSQL version: 9.2.4
> Operating system: WIN 8
> Descrip
The following bug has been logged on the website:
Bug reference: 8061
Logged by: Claudio Oliveira
Email address: claudio...@hotmail.com
PostgreSQL version: 9.2.4
Operating system: WIN 8
Description:
select count(*) from teste; --- 5000
select count(*) from teste limit
Em Sex, 2013-04-12 às 04:39 +, rajuk...@gmail.com escreveu:
> The following bug has been logged on the website:
>
> Bug reference: 8057
> Logged by: Raju
> Email address: rajuk...@gmail.com
> PostgreSQL version: 9.2.0
> Operating system: windows 7
> Description:
>
On 2013-04-12 10:47:52 -0400, Tom Lane wrote:
> Andres Freund writes:
> > Thats caused by the fact that you didn't do anything that forces a WAL
> > flush since you didn't do any inserts or such. If you would do any
> > DML in the nextval() calling transaction this shouldn't happen (unless
> > you
Andres Freund writes:
> Thats caused by the fact that you didn't do anything that forces a WAL
> flush since you didn't do any inserts or such. If you would do any
> DML in the nextval() calling transaction this shouldn't happen (unless
> you use synchronous_commit=off).
> Now, there's a legitimat
dan...@heroku.com writes:
> We have a somewhat high-churn table acting as a queue, and over time it's
> grown to be something like a gigabyte. I surmised it might be vanilla
> bloat, but the truth seems somewhat more exotic because both VACUUM FULL and
> CLUSTER generated absolutely no new free sp
On 2013-04-12 08:34:24 +, dan...@heroku.com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8058
> Logged by: Daniel Farina
> Email address: dan...@heroku.com
> PostgreSQL version: 9.0.13
> Operating system: Ubuntu 10.04
> Description:
On 2013-04-12 12:27:01 +, tar...@gmail.com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8059
> Logged by: Tarvi Pillessaar
> Email address: tar...@gmail.com
> PostgreSQL version: 9.2.4
> Operating system: linux
> Description:
>
> V
The following bug has been logged on the website:
Bug reference: 8057
Logged by: Raju
Email address: rajuk...@gmail.com
PostgreSQL version: 9.2.0
Operating system: windows 7
Description:
Dear Sir,
I am unable to connect postgresSQL from local machine to database on
s
Hi All,
I hit a hang issue in postgres 8.4 query. Hit this issue multiple time on
HP-UX. Below is the snapshot of the hang thread.
lwpid : 600943
---
0: c054ced0 : _poll_sys() + 0x30 (/usr/lib/hpux64/libc.so.1)
1: c
The following bug has been logged on the website:
Bug reference: 8060
Logged by: Shaun McCrery
Email address: shaun.c.mccr...@saic.com
PostgreSQL version: 9.2.4
Operating system: Server 2008 R2 x64
Description:
I upgraded to 9.2.4 and now the postgresql service is not
The following bug has been logged on the website:
Bug reference: 8059
Logged by: Tarvi Pillessaar
Email address: tar...@gmail.com
PostgreSQL version: 9.2.4
Operating system: linux
Description:
Very simple example:
postgres@sbox /usr/local/pgsql $ /usr/local/pgsql/bin
The following bug has been logged on the website:
Bug reference: 8058
Logged by: Daniel Farina
Email address: dan...@heroku.com
PostgreSQL version: 9.0.13
Operating system: Ubuntu 10.04
Description:
We have a somewhat high-churn table acting as a queue, and over time
25 matches
Mail list logo
