The following bug has been logged on the website:
Bug reference: 7851
Logged by: ivano luberti
Email address: lube...@archicoop.it
PostgreSQL version: 8.4.15
Operating system: Windows 7 Home Premium 64 bits
Description:
I know this is probalby a duplicate of bug BUG #
The following bug has been logged on the website:
Bug reference: 7850
Logged by: Nadir Vardar
Email address: nvar...@carrieriq.com
PostgreSQL version: 9.0.10
Operating system: linux-gridsql
Description:
I am trying to run below query;
SELECT
tbl.id,
tbl.day,
Hello
this is not a bug report.
please, send your query to pg_general mailing list
probably better - ask on gridsql mailing list
Regards
Pavel Stehule
2013/2/5 :
> The following bug has been logged on the website:
>
> Bug reference: 7850
> Logged by: Nadir Vardar
> Email addres
On Tue, Feb 5, 2013 at 10:45 AM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 7851
> Logged by: ivano luberti
> Email address: lube...@archicoop.it
> PostgreSQL version: 8.4.15
> Operating system: Windows 7 Home Premium 64 bits
> Description:
Tuesday, February 05, 2013 12:40 PM nvardar wrote:
> I am trying to run below query;
>
> SELECT
> tbl.id,
> tbl.day,
> tbl.week,
> tbl.appfailure,
> tbl.appname,
> tbl.deviceid,
> ext6.DIM_NAME,
> ext7.DIM_NAME,
> ext8.DIM_NAME,
> ext9.DIM_NAME,
> tbl.st
On 5 February 2013 17:06, Amit Kapila wrote:
> Tuesday, February 05, 2013 12:40 PM nvardar wrote:
> > throws;
> >
> > >[Error] Script lines: 1-20 -
> > ERROR: Node 2 has aborted execution, cause is:
> > com.edb.gridsql.exception.XDBServerException :
> > java.lang.NullPoin
The following bug has been logged on the website:
Bug reference: 7852
Logged by: Yogesh Khandelwal
Email address: yogesh.khandel...@emc.com
PostgreSQL version: 9.0.8
Operating system: Linux
Description:
hi,
I've deployed TeamPostgreSQL on my server and trying to acce
On Feb 5, 2013 6:20 PM, wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 7852
> Logged by: Yogesh Khandelwal
> Email address: yogesh.khandel...@emc.com
> PostgreSQL version: 9.0.8
> Operating system: Linux
> Description:
>
> hi,
>
> I've deployed
The following bug has been logged on the website:
Bug reference: 7853
Logged by: James Skaggs
Email address: jim...@seagate.com
PostgreSQL version: 8.4.14
Operating system: RHEL6
Description:
After "analyze verbose", the table shows 158 million rows. A select count(1)
Thanks Dave for your quick answer
Il 05/02/2013 16:19, Dave Page ha scritto:
If this is a new installation, you should really use 9.2. 8.4 will go
out of support in about a year.
It is a new installation on my machine, but I use for development and I
have to support customers that will still
Thanks Dave for your quick answer
Il 05/02/2013 16:19, Dave Page ha scritto:
If this is a new installation, you should really use 9.2. 8.4 will go
out of support in about a year.
It is a new installation on my machine, but I use for development and I
have to support customers that will still
"jim...@seagate.com" wrote:
> INFO: analyzing "public.stream_file"
> INFO: "stream_file": scanned 3 of 2123642 pages, containing
> 184517 live rows and 2115512 dead rows; 3 rows in sample,
> 158702435 estimated total rows
184517 live rows in 3 randomly sampled pages out of 2123642
Kevin -
Agreed, we shouldn't have so many dead rows. Our autovacuum is set on but
has default parameters. We are clustering today. This, of course, means
downtime and inconvenience to the users.
Here is the troublesome query:
select
sum(case when t1.cdlc < 0 then 0 else t1.cdlc end) as
James R Skaggs wrote:
> Agreed, we shouldn't have so many dead rows. Our autovacuum is
> set on but has default parameters. We are clustering today.
> This, of course, means downtime and inconvenience to the users.
Right, which is why it's important to figure out why the bloat
happened. Som
14 matches
Mail list logo
