Nithya Soman wrote
> Hi
>
> Could you please provide any method (query or any logfile) to check
> max connections happened during a time interval in psql DB ?
Only if the time interval desired in basically zero-width (i.e.,
instantaneous). The "pg_stat_activity" view is your friend in this.
You
Thanks Bruce. Really interesting, but, I show zone reclaim is already
turned off on our system.
root@site-db01b:~ # numactl --hardware
available: 2 nodes (0-1)
node 0 cpus: 0 1 2 3 4 5 12 13 14 15 16 17
node 0 size: 393181 MB
node 0 free: 467 MB
node 1 cpus: 6 7 8 9 10 11 18 19 20 21 22 23
node 1
On 3/26/2014 1:07 PM, Hall, Samuel L (Sam) wrote:
ERROR: syntax error at or near "LIKE"
LINE 2: CREATE TABLE tse_history_old (LIKE tse_history)
thats the syntax from
http://www.postgresql.org/docs/current/static/sql-createtable.html
try it in psql instead of pgadmin ?
earlier, you menti
Hall, Samuel L (Sam) wrote:
> ERROR: syntax error at or near "LIKE"
> LINE 2: CREATE TABLE tse_history_old (LIKE tse_history)
>
> ^
Note it says this is on line 2. What have you got in the previous line?
(psql has \p
On 03/26/2014 02:13 PM, Hall, Samuel L (Sam) wrote:
Yes
"PostgreSQL 9.3.0 on x86_64-unknown-linux-gnu, compiled by gcc (Ubuntu/Linaro
4.6.3-1ubuntu5) 4.6.3, 64-bit"
So what happens when you run the command from psql ?
--
Adrian Klaver
adrian.kla...@aklaver.com
--
Sent via pgsql-general m
Yes
"PostgreSQL 9.3.0 on x86_64-unknown-linux-gnu, compiled by gcc (Ubuntu/Linaro
4.6.3-1ubuntu5) 4.6.3, 64-bit"
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Wednesday, March 26, 2014 4:03 PM
To: Hall, Samuel L (Sam)
Cc: John R Pierce; pgsql-general@postgresql.org
"Hall, Samuel L (Sam)" writes:
> ERROR: syntax error at or near "LIKE"
> LINE 2: CREATE TABLE tse_history_old (LIKE tse_history)
You're certain the server you're talking to is 9.3?
("SELECT version()" is a good way to be sure.)
regards, tom lane
--
Sent via pgsql-gene
On Wed, Mar 26, 2014 at 08:22:01PM +, Anand Kumar, Karthik wrote:
> Looking a little deeper, I saw signs of memory being heavily fragmented:
>
> root@site-db01b:/var/log # cat /proc/buddyinfo
> Node 0, zone DMA 1 1 2 2 2 1 0 0 1 1 3
> Node 0, zone DMA32 8 7 8 7 10 8 7 11 9 5 92
> Node 0, zone
Hi all,
We finally made some headway on this - we noticed messages like the below
in /var/log/messages whenever the issue happened:
Mar 26 07:39:58 site-db01b kernel: postmaster: page allocation failure.
order:1, mode:0x20
Mar 26 07:39:58 site-db01b kernel: Pid: 39066, comm: postmaster Not
tainte
ERROR: syntax error at or near "LIKE"
LINE 2: CREATE TABLE tse_history_old (LIKE tse_history)
^
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of John R Pierce
Sent: Wedn
On 3/26/2014 12:58 PM, Hall, Samuel L (Sam) wrote:
That doesn't help. Even this CREATE TABLE tse_history_old (LIKE
tse_history) gives an error
the exact same error ?
--
john r pierce 37N 122W
somewhere on the middle of the left coast
On Thu, Mar 27, 2014 at 1:31 AM, John R Pierce wrote:
> why don't you ask the Fortify vendor ?
Yup, following up with them in parallel.
Search didn't gave me any good links, so wanted to check with community too
here.
If not Fortify, is there any other such tool?
Regards...
On 3/26/2014 12:42 PM, Dev Kumkar wrote:
Is Fortify supported for PostgreSQL?
why don't you ask the Fortify vendor ?
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.o
That doesn't help. Even this CREATE TABLE tse_history_old (LIKE tse_history)
gives an error
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of John R Pierce
Sent: Wednesday, March 26, 2014 2:43 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENER
On Wed, Mar 26, 2014 at 11:01:28AM +0530, Nithya Soman wrote:
> Hi
>
> Could you please provide any method (query or any logfile) to check
> max connections happened during a time interval in psql DB ?
I think there will be a message in the logs when you exceed
max_connections. I think the error
On 3/26/2014 12:32 PM, Hall, Samuel L (Sam) wrote:
When I try to run SQL from PgAdmin : CREATE TABLE tse_history_old LIKE
tse_history INCLUDING ALL WITH OIDS
I get this error
ERROR: syntax error at or near "LIKE"
LINE 2: CREATE TABLE tse_history_old LIKE tse_history INCLUDING ALL ...
f
Is Fortify supported for PostgreSQL?
Any auditing tool which you suggest to check the schema design, roles and
functions and other aspects?
I have used fortify for oracle and sybase, but just not sure about
postgreSQL?
Can anyone provide some pointers here and if not Fortify then any such tool?
I know this isn't exactly what you're looking for (a query or log), but we
use this tool to monitor our connections and alert when they hit a
particular threshold:
http://bucardo.org/check_postgres/check_postgres.pl.html#backends
On Wed, Mar 26, 2014 at 12:31 AM, Nithya Soman
wrote:
> Hi
>
> Co
When I try to run SQL from PgAdmin : CREATE TABLE tse_history_old LIKE
tse_history INCLUDING ALL WITH OIDS
I get this error
ERROR: syntax error at or near "LIKE"
LINE 2: CREATE TABLE tse_history_old LIKE tse_history INCLUDING ALL ...
testing, I find that using the word "LIKE" always causes erro
On Mar 25, 2014, at 3:30 PM, Carlos Espejo wrote:
> Anybody running their PostgreSQL server from a ecryptfs container? What are
> the common production setups out there? What are the drawbacks that people
> have experienced with their solution?
We run postgres on XFS on lvm volumes put
Hi
Could you please provide any method (query or any logfile) to check
max connections happened during a time interval in psql DB ?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Wed, Mar 26, 2014 at 11:43 AM, Tom Lane wrote:
> In principle I guess we could somehow merge the stats of y and z
> when looking at a "coalesce(y, z)" expression, but I'm not sure
> how that would work exactly.
Yeah, I'm not sure there's anything to fix here, either. Just a
reminder that coale
On Mar 26, 2014, at 9:04 AM, Jeff Janes wrote:
> On Tue, Mar 25, 2014 at 6:33 PM, Jeff Janes wrote:
> On Tuesday, March 25, 2014, Steven Schlansker wrote:
> Hi everyone,
>
> I have a Postgres 9.3.3 database machine. Due to some intelligent work on
> the part of someone who shall remain name
On Mar 25, 2014, at 7:58 PM, Adrian Klaver wrote:
> On 03/25/2014 04:52 PM, Steven Schlansker wrote:
>>
>
>>> Some more questions, what happens when things begin to dawn on me:)
>>>
>>> You said the disk filled up entirely with log files yet currently the
>>> number(size) of logs is growing.
Brian Crowell writes:
> Which says to me coalesce has a selectivity.
Well, the point is you're just getting a default selectivity estimate
for the "acc.rule_set_id = coalesce(...anything...)" condition. The
planner is smarter about plain "x = y" join conditions: it looks up
the column stats for
On Tue, Mar 25, 2014 at 6:33 PM, Jeff Janes wrote:
> On Tuesday, March 25, 2014, Steven Schlansker wrote:
>
>> Hi everyone,
>>
>> I have a Postgres 9.3.3 database machine. Due to some intelligent work
>> on the part of someone who shall remain nameless, the WAL archive command
>> included a '>
On Wed, Mar 26, 2014 at 10:23 AM, Tom Lane wrote:
> Hm. It's not obvious from here that those give the same results ---
> but you probably understand your schema better than the rest of us.
The _users table has a "user_id", and a nullable column
"impersonating" which refers to a user_id you want
Brian Crowell writes:
> Here's what I did, though. I collapsed the pl2.current_user view into
> pl2.visible_accounts:
> ===
> select
> acc.account,
> acc.manager,
> acc.is_fund
> from pl2._visible_accounts_by_rule_set acc
> inner join (pl2._users u
> left join pl2._users iu on
On Tue, Mar 25, 2014 at 5:59 PM, Tom Lane wrote:
> Yeah. The weird thing about that is that the nestloop rowcount estimate
> isn't the product of the two input rowcounts --- you'd sort of expect an
> estimate of 158 given the input-relation sizes. While that's not ipso
> facto evidence of a bug
On 03/25/2014 05:23 PM, Sam Saffron wrote:
Sorry, its part of a rather elaborate docker based upgrade, that
install is just done to get the binaries, the data is all in a
completely different location which is untouched.
So there are two instances of 9.2 in play at one time?
The upgrade process
Hi All,
This one is just for the record/search: it is solved.
But it is quite rare i think.
May save others time.
PostgreSQL for Windows setup.
While trying to connect the client errors with:
Could not connect to the server. Reason: could not receive data from
server: Software caused connectio
Oscar Calderon wrote:
> Everybody have a nice day. Well, finally the place where i currently work
> paid me a chance to take the
> Associate Certification exam and i'm reviewing some topics, specifically the
> topics that the exam
> covers (some of them are easy to me like psql, which i use almos
32 matches
Mail list logo
