Re: [GENERAL] Why are data files stored in /var/lib

Hello Manuel > -Original Message- > From: Manuel Gómez [mailto:tar...@gmail.com] > Sent: Samstag, 30. April 2016 05:45 > To: Charles Clavadetscher > Cc: Postgres General > Subject: Re: [GENERAL] Why are data files stored in

Re: [GENERAL] How to manually force a transaction wraparound

On Sat, Apr 30, 2016 at 02:16:48PM +1200, Thomas Munro wrote: > Take a look at the script repro-bogus-subtrans-error-wraparound.sh > from this email: I wonder whether something like this (and other "beat it up" kinds of tools) ought to be in contrib/ or in some sort of well-known project

Re: [GENERAL] Why are data files stored in /var/lib

On Fri, Apr 29, 2016 at 11:00 PM, Charles Clavadetscher wrote: > I had a discussion yesterday with some friends, who are sysadmins about the > location of database files. In a default installation > from a distribution (apt-get install) PostgreSQL creates a cluster

[GENERAL] Why are data files stored in /var/lib

Hello I use version 9.5 on Linux Mint 17.3. I had a discussion yesterday with some friends, who are sysadmins about the location of database files. In a default installation from a distribution (apt-get install) PostgreSQL creates a cluster unter /var/lib/. According to my colleagues /var/lib

Re: [GENERAL] How to manually force a transaction wraparound

On Sat, Apr 30, 2016 at 10:48 AM, Eric Ridge wrote: > I want to force my database to wraparound, just to see what happens. How > can I do this without consuming a few billion transactions? Take a look at the script repro-bogus-subtrans-error-wraparound.sh from this email:

Re: [GENERAL] Allow disabling folding of unquoted identifiers to lowercase

John McKown writes: > ​Oh well, it's been interesting, but I don't think that we'll come to a > resolution for the OP on this issue. I just blame both PostgreSQL and MySQL > for this problem because the SQL standard says that the names are > automatically

Re: [GENERAL] Postgres processes getting stuck (bug?)

On Fri, Apr 29, 2016 at 1:09 PM, John R Pierce wrote: > On 4/29/2016 10:30 AM, Ciprian Grigoras wrote: > > We're running Postgresql 9.0.7... > > > do note, the 9.0 series got up to 9.0.23 before it was discontinued last > year. 9.0.7 was released in February 2012, 4+ years

Re: [GENERAL] Allow disabling folding of unquoted identifiers to lowercase

On Fri, Apr 29, 2016 at 3:38 PM, John R Pierce wrote: > On 4/29/2016 12:56 PM, John McKown wrote: > > I suspect this would be painful for the parser, unless you also enforced >> that all SQL keywords were in a specific case (all lower would be the >> minimal impact to the

Re: [GENERAL] Allow disabling folding of unquoted identifiers to lowercase

On Fri, Apr 29, 2016 at 3:38 PM, John R Pierce wrote: > On 4/29/2016 12:56 PM, John McKown wrote: > > I suspect this would be painful for the parser, unless you also enforced >> that all SQL keywords were in a specific case (all lower would be the >> minimal impact to the

Re: [GENERAL] Allow disabling folding of unquoted identifiers to lowercase

On 4/29/2016 12:56 PM, John McKown wrote: I suspect this would be painful for the parser, unless you also enforced that all SQL keywords were in a specific case (all lower would be the minimal impact to the code). otherwise the parser would have to lower() every token to check

Re: [GENERAL] Allow disabling folding of unquoted identifiers to lowercase

On Fri, Apr 29, 2016 at 2:44 PM, John R Pierce wrote: > On 4/29/2016 10:21 AM, Evgeny Morozov wrote: > > It would be great if Postgres had a server setting that allowed the > automatic folding of identifiers to lowercase to be disabled, so that camel > case identifiers could

Re: [GENERAL] Postgres processes getting stuck (bug?)

Thanks everyone, it could be that the Linux server is problematic (it's got a long uptime). I ran the strace thing, 1. [root@box ~]# strace -p 20825 2. Process 20825 attached - interrupt to quit 3. connect(90, {sa_family=AF_FILE, path="/var/centrifydc/daemon2"}, 25 and it kept

Re: [GENERAL] Primary Keys

On 04/29/2016 11:07 AM, Dustin Kempter wrote: Hi all, Is there a query I can run that will scan through all the tables of a database and give me a list of all tables without a primary key? Im not having any luck with this. Two options: First

Re: [GENERAL] Allow disabling folding of unquoted identifiers to lowercase

On 4/29/2016 10:21 AM, Evgeny Morozov wrote: It would be great if Postgres had a server setting that allowed the automatic folding of identifiers to lowercase to be disabled, so that camel case identifiers could be used without having to quote every single identifier, i.e. SELECT MyColumn

[GENERAL] Allow disabling folding of unquoted identifiers to lowercase

It would be great if Postgres had a server setting that allowed the automatic folding of identifiers to lowercase to be disabled, so that camel case identifiers could be used without having to quote every single identifier, i.e. SELECT MyColumn FROM MyTable ORDER BY MyColumn instead of SELECT

Re: [GENERAL] Postgres processes getting stuck (bug?)

Ciprian Grigoras writes: > Hi guys, > > I had a question. We're running Postgresql 9.0.7 , and all of a sudden we > started seeing unexpected behavior. One table got locked after we ran one > simple INSERT on one > test item. > Nothing else was running against that

Re: [GENERAL] Primary Keys

On Fri, Apr 29, 2016 at 1:20 PM, Melvin Davidson wrote: > > > On Fri, Apr 29, 2016 at 2:07 PM, Dustin Kempter < > dust...@consistentstate.com> wrote: > >> Hi all, >> Is there a query I can run that will scan through all the tables of a >> database and give me a list of all

Re: [GENERAL] Primary Keys

On Fri, Apr 29, 2016 at 2:07 PM, Dustin Kempter wrote: > Hi all, > Is there a query I can run that will scan through all the tables of a > database and give me a list of all tables without a primary key? Im not > having any luck with this. > > Thanks in advance! > >

Re: [GENERAL] Postgres processes getting stuck (bug?)

On 4/29/2016 10:30 AM, Ciprian Grigoras wrote: We're running Postgresql 9.0.7... do note, the 9.0 series got up to 9.0.23 before it was discontinued last year. 9.0.7 was released in February 2012, 4+ years ago. 9.0.18 fixed some index corruption bugs in GIST indexes, 9.0.15 fixed a bunch

[GENERAL] Primary Keys

Hi all, Is there a query I can run that will scan through all the tables of a database and give me a list of all tables without a primary key? Im not having any luck with this. Thanks in advance! -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your

Re: [GENERAL] Postgres processes getting stuck (bug?)

Check the wait state for the backend process. I’ve seen this happen when a process ran a per-row trigger that tried to connect to something else, and it filled the ip_conntrack table. So, kernel level wait along with a whole bunch of locks on the table in question. Running

[GENERAL] Postgres processes getting stuck (bug?)

Hi guys, I had a question. We're running Postgresql 9.0.7 , and all of a sudden we started seeing unexpected behavior. One table got locked after we ran one simple INSERT on one test item. Nothing else was running against that table as far as we know, and the query is frozen there now. After some

[GENERAL] PostgreSQL proxying

Hello folks! :-) hope I'm not OT here Need an advise here. I have a PostgreSQL cluster that should be accessed in two ways: - By a Web Services system (always same host in my vLAN, and that is simple) - By a replicator (any host, with unpredictable IP) In my previous configuration I had a

Re: [GENERAL] Does this perf output seem 'normal'?

I believe the library is spawning a new connection for each query so that makes perfect sense. I will see what improvements can be made at the application layer and look at using pgbouncer if required =) Thank you for sharing your knowledge! -- Sent via pgsql-general mailing list

Re: [GENERAL] Issue during postgresql startup

Dear All, I am sharing my further observation regarding the system behavior. The errors related to this missing table file started coming from 2016-04-24 20:37:11 till the end when pg_xlog filled up the disk space and postgres crashed eventually. postgresql_log.Sun.gz:<%2016-04-24 20:37:11