pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedHi!
6+ messages / 5 participants
[nested] [flat]
* Hi!
@ 2004-06-20 16:39 Janio Rosa da Silva <janio_2003@yahoo.com.br>
2004-06-22 16:23 ` Re: Hi! Josh Berkus <josh@agliodbs.com>
0 siblings, 1 reply; 6+ messages in thread
From: Janio Rosa da Silva @ 2004-06-20 16:39 UTC (permalink / raw)
To: pgsql-performance
Hi,
I am trying install the postgresql-7.4.3 simple installation. I did ./configure command at the postgresql directory source. While the configuring proccess I receiving the follow message:
checking for tar... /bin/tar
checking for strip... strip
checking whether it is possible to strip libraries... yes
checking for bison... bison -y
*** The installed version of Bison is too old. PostgreSQL needs
*** Bison version 1.875 or later.
checking for perl... /usr/bin/perl
checking for main in -lbsd... no
checking for setproctitle in -lutil... no
checking for main in -lm... yes
But, after this message the install proccess continue like this message. The problem is that the installation never finish. I am thinking that the configure proccess is in loop. Have it anything relation with my hardware configuration? The computer where I did this is: AMD K6-II 200 MHZ; 64 MB memory;
I would like why the configure proccess never finish.
Regards,
Janio
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Hi!
2004-06-20 16:39 Hi! Janio Rosa da Silva <janio_2003@yahoo.com.br>
@ 2004-06-22 16:23 ` Josh Berkus <josh@agliodbs.com>
0 siblings, 0 replies; 6+ messages in thread
From: Josh Berkus @ 2004-06-22 16:23 UTC (permalink / raw)
To: Janio Rosa da Silva <janio_2003@yahoo.com.br>; pgsql-performance
Janio,
> I am trying install the postgresql-7.4.3 simple installation. I did
> ./configure command at the postgresql directory source. While the
> configuring proccess I receiving the follow message:
This is the wrong list for this question. Please try PGSQL-ADMIN. You're
much more likely to get help there.
Sorry!
--
Josh Berkus
Aglio Database Solutions
San Francisco
^ permalink raw reply [nested|flat] 6+ messages in thread
* Hi
@ 2017-04-13 06:25 Daulat Ram <Daulat.Ram@cyient.com>
2017-04-13 08:21 ` Re: Hi Glyn Astill <glynastill@yahoo.co.uk>
0 siblings, 1 reply; 6+ messages in thread
From: Daulat Ram @ 2017-04-13 06:25 UTC (permalink / raw)
To: pgsql-performance
Hello,
I need to know the criteria behind for settings the work_mem in PostgreSQL, please give the example also if possible.
Regards,
Daulat
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Hi
2017-04-13 06:25 Hi Daulat Ram <Daulat.Ram@cyient.com>
@ 2017-04-13 08:21 ` Glyn Astill <glynastill@yahoo.co.uk>
0 siblings, 0 replies; 6+ messages in thread
From: Glyn Astill @ 2017-04-13 08:21 UTC (permalink / raw)
To: Daulat Ram <Daulat.Ram@cyient.com>; pgsql-performance
> From: Daulat Ram <Daulat.Ram@cyient.com>
> To: "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
> Sent: Thursday, 13 April 2017, 7:25
> Subject: [PERFORM] Hi
>
> Hello,
>
> I need to know the criteria behind for settings the work_mem in PostgreSQL, please give the example also if possible.
>
> Regards,
> Daulat
Is there anything in particular from the manual pages you don't understand? It should be quite clear:
https://www.postgresql.org/docs/current/static/runtime-config-resource.html
"Specifies the amount of memory to be used by internal sort operations and hash tables before writing to temporary disk files. The value defaults to four megabytes (4MB). Note that for a complex query, several sort or hash operations might be running in parallel; each operation will be allowed to use as much memory as this value specifies before it starts to write data into temporary files."
"Also, several running sessions could be doing such operations concurrently. Therefore, the total memory used could be many times the value of work_mem; it is necessary to keep this fact in mind when choosing the value. Sort operations are used for ORDER BY, DISTINCT, and merge joins. Hash tables are used in hash joins, hash-based aggregation, and hash-based processing of IN subqueries."
Glyn
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Hi
@ 2017-08-25 06:49 Daulat Ram <Daulat.Ram@cyient.com>
2017-08-25 14:42 ` Re: Hi David G. Johnston <david.g.johnston@gmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: Daulat Ram @ 2017-08-25 06:49 UTC (permalink / raw)
To: pgsql-performance
Hello,
Would I request to help me on this query.
SELECT 'Inspection Completed' as "ALL Status" ,COUNT(*) as "Number of Count" FROM ud_document WHERE status = 'Inspection Completed' union SELECT 'Pending', COUNT(*) FROM ud_document WHERE status = 'Pending' union SELECT 'Approved', COUNT(*) FROM ud_document WHERE status = 'Approved' union SELECT 'Rejected', COUNT(*) FROM ud_document WHERE status = 'Rejected' union SELECT 'Payment Due',count(*) from ud_document where payment_status = 'Payment Due' union SELECT 'Payment Done' ,count(*) from ud_document where payment_status = 'Payment Done'
And now I want to exclude the uniqueid= '201708141701018' from the above query. how it can be ???
Regards,
Daulat
________________________________
DISCLAIMER:
This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Check all attachments for viruses before opening them. All views or opinions presented in this e-mail are those of the author and may not reflect the opinion of Cyient or those of our affiliates.
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Hi
2017-08-25 06:49 Re: Hi Daulat Ram <Daulat.Ram@cyient.com>
@ 2017-08-25 14:42 ` David G. Johnston <david.g.johnston@gmail.com>
0 siblings, 0 replies; 6+ messages in thread
From: David G. Johnston @ 2017-08-25 14:42 UTC (permalink / raw)
To: Daulat Ram <Daulat.Ram@cyient.com>; +Cc: pgsql-performance
On Thu, Aug 24, 2017 at 11:49 PM, Daulat Ram <Daulat.Ram@cyient.com> wrote:
> Hello,
>
>
>
> Would I request to help me on this query.
>
>
>
> SELECT 'Inspection Completed' as "ALL Status" ,COUNT(*) as "Number of
> Count" FROM ud_document WHERE status = 'Inspection Completed' union SELECT
> 'Pending', COUNT(*) FROM ud_document WHERE status = 'Pending' union SELECT
> 'Approved', COUNT(*) FROM ud_document WHERE status = 'Approved' union
> SELECT 'Rejected', COUNT(*) FROM ud_document WHERE status = 'Rejected'
> union SELECT 'Payment Due',count(*) from ud_document where payment_status =
> 'Payment Due' union SELECT 'Payment Done' ,count(*) from ud_document where
> payment_status = 'Payment Done'
>
>
>
> And now I want to exclude the uniqueid= '201708141701018' from the above
> query. how it can be ???
>
>
>
Your use of UNION here seems necessary. Just write a normal GROUP BY
aggregation query. You might need to get a bit creative since you are
collapsing status and payment_status into a single column. "CASE ... WHEN
... THEN ... ELSE ... END" is quite helpful for doing stuff like that. For
now I'll just leave them as two columns.
SELECT status, payment_status, count(*)
FROM ud_document
WHERE uniqueid <> '201708141701018'
GROUP BY 1, 2;
David J.
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2017-08-25 14:42 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-06-20 16:39 Hi! Janio Rosa da Silva <janio_2003@yahoo.com.br>
2004-06-22 16:23 ` Josh Berkus <josh@agliodbs.com>
2017-04-13 06:25 Hi Daulat Ram <Daulat.Ram@cyient.com>
2017-04-13 08:21 ` Re: Hi Glyn Astill <glynastill@yahoo.co.uk>
2017-08-25 06:49 Re: Hi Daulat Ram <Daulat.Ram@cyient.com>
2017-08-25 14:42 ` Re: Hi David G. Johnston <david.g.johnston@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox