[GENERAL] Revolut - postgres ?

https://blog.revolut.com/no-excuses-we-let-you-down-32f81e64f974 The career section of the company's web page lists PG as one of the tech stack. Would be interesting to know the details. "At around 07:00 BST on Friday morning, our transaction database began to malfunction. Naturally, we

[GENERAL] Inconsistent Postgres error when installing our product containing PostgreSQL 9.3.4

Hi, I'm getting inconsistent Postgres errors, when we upgrade our product that bundles PostgreSQL 9.3.4. We have 13 databases and we get errors at different places of the database setup. Here are the failures: 1. $POSTGRES/bin/psql -c " CREATE SEQUENCE serial1 START 1 CYCLE ;" -d $ARCHDB

Re: [GENERAL] storing postgres data on dropbox

On 06/18/2017 01:13 PM, Martin Mueller wrote: I think I get it. 'base' is not the data directory but a child of var-9.5, which (with its entire path) is the "data directory". I honestly don't recall how I installed Posgres, but I'm pretty sure that I picked the default method from the

Re: [GENERAL] storing postgres data on dropbox

I think I get it. 'base' is not the data directory but a child of var-9.5, which (with its entire path) is the "data directory". I honestly don't recall how I installed Posgres, but I'm pretty sure that I picked the default method from the Postgres. Many thanks for your help, which is

Re: [GENERAL] storing postgres data on dropbox

On 06/18/2017 01:00 PM, Martin Mueller wrote: Did you mean that "/users/martin/Library ApplicationSupport/Postgres/var9.5/base/" is above or below the data directory? As I understand it Postgres is the highest Postgres specific directory. It contains just one child directory, var-9.5, which

Re: [GENERAL] storing postgres data on dropbox

Did you mean that "/users/martin/Library ApplicationSupport/Postgres/var9.5/base/" is above or below the data directory? As I understand it Postgres is the highest Postgres specific directory. It contains just one child directory, var-9.5, which has a lot of subdirectories, including

Re: [GENERAL] storing postgres data on dropbox

On 06/18/2017 11:29 AM, Martin Mueller wrote: How close is close enough? In my case, the machines run OS Sierra, and the installation uses the same directory paths Keeping the Postgres version in sync should be simple. Is that close enough? In MySQL you can copy and paste individual tables if

Re: [GENERAL] storing postgres data on dropbox

On Sun, Jun 18, 2017 at 06:29:50PM +, Martin Mueller wrote: > How close is close enough? In my case, the machines run OS > Sierra, and the installation uses the same directory paths > Keeping the Postgres version in sync should be simple. Is > that close enough? I am not an expert on that.

Re: [GENERAL] storing postgres data on dropbox

On Sun, Jun 18, 2017 at 06:29:50PM +, Martin Mueller wrote: > In MySQL you can copy and paste individual tables if the > data are kept in ISAM, but INNO is hopeless that way. Is > Postgres more like INNO than ISAM when it comes to table > storage? *more* like INNO but not at all *like* INNO

Re: [GENERAL] storing postgres data on dropbox

How close is close enough? In my case, the machines run OS Sierra, and the installation uses the same directory paths Keeping the Postgres version in sync should be simple. Is that close enough? In MySQL you can copy and paste individual tables if the data are kept in ISAM, but INNO is

Re: [GENERAL] storing postgres data on dropbox

> On Jun 18, 2017, at 10:58 AM, Karsten Hilbert wrote: > > On Sun, Jun 18, 2017 at 05:30:44PM +, Martin Mueller wrote: > >> Thank for this very helpful answer, which can be >> implemented for less than $100. For somebody who started >> working a 128k Mac in the

Re: [GENERAL] storing postgres data on dropbox

On Sun, Jun 18, 2017 at 05:30:44PM +, Martin Mueller wrote: > Thank for this very helpful answer, which can be > implemented for less than $100. For somebody who started > working a 128k Mac in the eighties, it is mindboggling that > for that amount you can buy a terabyte of storage in a

Re: [GENERAL] storing postgres data on dropbox

Thank for this very helpful answer, which can be implemented for less than $100. For somebody who started working a 128k Mac in the eighties, it is mindboggling that for that amount you can buy a terabyte of storage in a device that you put in a coat pocket. I'll read up on rsync On

Re: [GENERAL] storing postgres data on dropbox

On Sun, Jun 18, 2017 at 13:16:16 +, Martin Mueller wrote: Why not a PostgreSQL-database somewhere in the cloud? Good question, but it's a question of money and performance. I used MySQL for many years and then moved a dataset to an instance on AWS. The

Re: [GENERAL] storing postgres data on dropbox

On 06/18/2017 06:16 AM, Martin Mueller wrote: Why not a PostgreSQL-database somewhere in the cloud? Good question, but it's a question of money and performance. I used MySQL for many years and then moved a dataset to an instance on AWS. The performance was horribly slow. Then some kind soul at

Re: [GENERAL] storing postgres data on dropbox

Why not a PostgreSQL-database somewhere in the cloud? Good question, but it's a question of money and performance. I used MySQL for many years and then moved a dataset to an instance on AWS. The performance was horribly slow. Then some kind soul at my institution hooked me up with "Aurora,"

Re: [GENERAL] storing postgres data on dropbox

Am 18.06.2017 um 03:03 schrieb Martin Mueller: This is a queestion from a Postgresql novice. I use Postgresql in a single-user environment on a Mac with OS Sierra. I use AquaFold DataStudio as a client, which is nice but also keeps me woefully ignorant about many aspects of the underlying

[GENERAL] storing postgres data on dropbox

This is a queestion from a Postgresql novice. I use Postgresql in a single-user environment on a Mac with OS Sierra. I use AquaFold DataStudio as a client, which is nice but also keeps me woefully ignorant about many aspects of the underlying application. As I understand it, Postgres data are

Re: [GENERAL] Locks Postgres

On Thu, Feb 9, 2017 at 9:00 PM, Patrick B wrote: > Hi guys > > I just wanna understand the locks in a DB server: > [image: Imagem inline 1] > > Access share = Does that mean queries were waiting because an > update/delete/insert was happening? > It would seem more

Re: [GENERAL] Locks Postgres

2017-02-10 18:18 GMT+13:00 John R Pierce : > On 2/9/2017 9:16 PM, John R Pierce wrote: > >> that spike in your graph suggests you had 8000 concurrent SELECT >> operations... >> > > errr, 7000, still way too many. > Thanks a lot John!! Got it PAtrick

Re: [GENERAL] Locks Postgres

On 2/9/2017 9:16 PM, John R Pierce wrote: that spike in your graph suggests you had 8000 concurrent SELECT operations... errr, 7000, still way too many. -- john r pierce, recycling bits in santa cruz -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to

Re: [GENERAL] Locks Postgres

On 2/9/2017 9:00 PM, Patrick B wrote: Access share = Does that mean queries were waiting because an update/delete/insert was happening? access share is taken by a SELECT, and all it blocks is an ACCESS EXCLUSIVE lock, which is taken by operations like ALTER TABLE, VACUUM FULL, and such

Re: [GENERAL] Locks Postgres

On 02/09/2017 09:00 PM, Patrick B wrote: Hi guys I just wanna understand the locks in a DB server: Imagem inline 1 Access share = Does that mean queries were waiting because an update/delete/insert was happening? https://www.postgresql.org/docs/9.3/static/explicit-locking.html I'm asking

[GENERAL] Locks Postgres

Hi guys I just wanna understand the locks in a DB server: [image: Imagem inline 1] Access share = Does that mean queries were waiting because an update/delete/insert was happening? I'm asking because I got a very big spike with > 30 seconds web response time. Running PG 9.3 Thanks! Patrick

Re: [GENERAL] R: Postgres 9.6.1 big slowdown by upgrading 8.4.22

FWIW you still haven't explained how the upgrade was performed. That might be a very important piece of information, because the 9.4 cluster might have hint bits set and/or the data may be mostly frozen, but the 9.6 cluster may not have that yet, resulting in higher CPU usage. We upgraded the

Re: [GENERAL] does postgres log the create/refresh of a materialized view anywhere?

On Wed, Dec 14, 2016 at 11:19 AM, Melvin Davidson wrote: > Originally, all I wanted was a column to record the creation date/time of an > object. One reason it was debunked was that it would lead > to a request for an additional column to record changes in objects. I >

Re: [GENERAL] does postgres log the create/refresh of a materialized view anywhere?

On Tue, Dec 13, 2016 at 8:50 PM, Kevin Grittner wrote: > On Tue, Dec 13, 2016 at 7:37 PM, Melvin Davidson > wrote: > > On Tue, Dec 13, 2016 at 7:36 PM, Kevin Grittner > wrote: > >> On Tue, Dec 13, 2016 at 5:57 PM, Jonathan Vanasco

Re: [GENERAL] does postgres log the create/refresh of a materialized view anywhere?

On Tue, Dec 13, 2016 at 7:37 PM, Melvin Davidson wrote: > On Tue, Dec 13, 2016 at 7:36 PM, Kevin Grittner wrote: >> On Tue, Dec 13, 2016 at 5:57 PM, Jonathan Vanasco wrote: >> >>> Is there a way to find out when a materialized view was

Re: [GENERAL] does postgres log the create/refresh of a materialized view anywhere?

On Tue, Dec 13, 2016 at 7:36 PM, Kevin Grittner wrote: > On Tue, Dec 13, 2016 at 5:57 PM, Jonathan Vanasco > wrote: > > > Is there a way to find out when a materialized view was > > created/refreshed? > > > I can log this manually in postgresql if needed,

Re: [GENERAL] does postgres log the create/refresh of a materialized view anywhere?

On Tue, Dec 13, 2016 at 5:57 PM, Jonathan Vanasco wrote: > Is there a way to find out when a materialized view was > created/refreshed? > I can log this manually in postgresql if needed, but was hoping > there was some "timestamp" on the view in a system table. This is not

[GENERAL] does postgres log the create/refresh of a materialized view anywhere?

Is there a way to find out when a materialized view was created/refreshed? I couldn't find this information anywhere in the docs. the use-case is that I wish to update a materialized view a few times a day in a clustered environment. i'd like to make sure one of the redundant nodes doesn't

Re: [GENERAL] Checking Postgres Streaming replication delay

On 10/31/16 3:39 PM, Patrick B wrote: |( ||extract(epoch FROMnow())- ||extract(epoch FROMpg_last_xact_replay_timestamp()) ||)::int lag| You could certainly simplify it though... extract(epoch FROM now()-pg_last_xact_replay_timestamp()) -- Jim Nasby, Data Architect, Blue Treble Consulting,

Re: [GENERAL] Checking Postgres Streaming replication delay

2016-10-31 15:54 GMT+13:00 Venkata B Nagothi : > > On Mon, Oct 31, 2016 at 11:57 AM, Patrick B > wrote: > >> Hi guys, >> >> I'm using this query to measure the delay between a Master and a >> Streaming Replication Slave server, using PostgreSQL 9.2.

Re: [GENERAL] Checking Postgres Streaming replication delay

On Mon, Oct 31, 2016 at 11:57 AM, Patrick B wrote: > Hi guys, > > I'm using this query to measure the delay between a Master and a Streaming > Replication Slave server, using PostgreSQL 9.2. > > SELECT >> pg_last_xlog_receive_location() receive, >>

[GENERAL] Checking Postgres Streaming replication delay

Hi guys, I'm using this query to measure the delay between a Master and a Streaming Replication Slave server, using PostgreSQL 9.2. SELECT > pg_last_xlog_receive_location() receive, > pg_last_xlog_replay_location() replay, > ( > extract(epoch FROM now()) - > extract(epoch FROM

Re: [GENERAL] Understanding Postgres Memory Usage

I've done the upgrade to 9.5. Memory bloat has reduced to a more manageable level. Most workers have an overhead of <20MB, with one outlier consuming 60MB. — Theron On Fri, Aug 26, 2016 at 5:41 AM, Tom Lane wrote: > Theron Luhn writes: > > Okay, I got a

Re: [GENERAL] Understanding Postgres Memory Usage

Theron Luhn writes: > Okay, I got a semi-reproducible test case: > https://gist.github.com/luhn/2b35a9b31255e3a6a2e6a06d1213dfc9 > The one caveat is that the memory rise only happens when using a > HashAggregate query plan (included in the gist), which I can't find a way > to

Re: [GENERAL] Understanding Postgres Memory Usage

Okay, I got a semi-reproducible test case: https://gist.github.com/luhn/2b35a9b31255e3a6a2e6a06d1213dfc9 The one caveat is that the memory rise only happens when using a HashAggregate query plan (included in the gist), which I can't find a way to get Postgres to reliably use. If you need it, I

Re: [GENERAL] Understanding Postgres Memory Usage

Theron Luhn writes: > Okay, here's the output: > https://gist.github.com/luhn/a39db625ba5eed90946dd4a196d12220 Hm, well the only thing there that looks even slightly out of the ordinary is the amount of free space in TopMemoryContext itself: TopMemoryContext: 3525712 total in

Re: [GENERAL] Understanding Postgres Memory Usage

On 8/25/2016 9:58 AM, Theron Luhn wrote: > I do not remember exact formula, but it should be something like “work_mem*max_connections + shared_buffers” and it should be around 80% of your machine RAM (minus RAM used by other processes and kernel). It will save you from OOM. a single query

Re: [GENERAL] Understanding Postgres Memory Usage

Hi Ilya, > Are you talking about buffers/cache increased? AFAIK this memory is used by kernel as buffer before any block device (HDD for example). If I'm reading the output correctly, buffers/cached do not increase. I'm looking at the 248MB -> 312MB under the "used" column in the "-/+

Re: [GENERAL] Understanding Postgres Memory Usage

Okay, here's the output: https://gist.github.com/luhn/a39db625ba5eed90946dd4a196d12220 — Theron On Thu, Aug 25, 2016 at 12:34 PM, Tom Lane wrote: > Theron Luhn writes: > >> It would be worth using plain old top to watch this process. We have > >> enough

Re: [GENERAL] Understanding Postgres Memory Usage

Theron Luhn writes: >> It would be worth using plain old top to watch this process. We have >> enough experience with that to be pretty sure how to interpret its >> numbers: "RES minus SHR" is the value to be worried about. > Sure thing. >

Re: [GENERAL] Understanding Postgres Memory Usage

> It would be worth using plain old top to watch this process. We have > enough experience with that to be pretty sure how to interpret its > numbers: "RES minus SHR" is the value to be worried about. Sure thing. https://gist.github.com/luhn/e09522d524354d96d297b153d1479c 13#file-top-txt RES -

Re: [GENERAL] Understanding Postgres Memory Usage

On Thu, Aug 25, 2016 at 1:25 PM, Tom Lane wrote: > Hmm. I find it mighty suspicious that the USS, PSS, and RSS numbers are > all increasing to pretty much the same tune, ie from very little to circa > 100MB. I think there is a decent chance that smem is not doing what it >

Re: [GENERAL] Understanding Postgres Memory Usage

Theron Luhn writes: >> If it's not an outright leak, it's probably consumption of cache space. >> We cache stuff that we've read from system catalogs, so sessions that >> touch lots of tables (like thousands) can grow due to that. Another >> possible source of large cache

Re: [GENERAL] Understanding Postgres Memory Usage

> 9.3.which? We do fix memory leaks from time to time ... 9.3.14 > If it's not an outright leak, it's probably consumption of cache space. > We cache stuff that we've read from system catalogs, so sessions that > touch lots of tables (like thousands) can grow due to that. Another > possible

Re: [GENERAL] Understanding Postgres Memory Usage

Theron Luhn writes: > I have an application that uses Postgres 9.3 as the primary datastore. 9.3.which? We do fix memory leaks from time to time ... > Some of these queries use quite a bit of memory. I've observed a > "high-water mark" behavior in memory usage: running a

Re: [GENERAL] Understanding Postgres Memory Usage

$ free -h # Before the query total used free sharedbuffers cached Mem: 7.8G 5.2G 2.6G 212M90M 4.9G -/+ buffers/cache: 248M 7.6G Swap: 0B 0B 0B $ free -h # After the query

[GENERAL] Understanding Postgres Memory Usage

I have an application that uses Postgres 9.3 as the primary datastore. Like any real-life application, it's not all roses—There are many ugly, convoluted, and inefficient queries. Some of these queries use quite a bit of memory. I've observed a "high-water mark" behavior in memory usage:

Re: [GENERAL] Unix Postgres 9.5. using pg_basebackup and WAL files. Can't get a PITR recovery

On Fri, Jul 15, 2016 at 10:09 AM, Pruett, Jennis wrote: > I can't cut and paste my issues, so I will explain as best I can. > > > > I’m testing PITR on a single 9.5 db (no replication setups). > > > > I have all the settings that I can find, wal_level, archive_command, >

[GENERAL] Unix Postgres 9.5. using pg_basebackup and WAL files. Can't get a PITR recovery

I can't cut and paste my issues, so I will explain as best I can. I'm testing PITR on a single 9.5 db (no replication setups). I have all the settings that I can find, wal_level, archive_command, restore_command, directories defined, logs defined. My WAL files are stored off in another area

Re: [GENERAL] Converting Postgres SQL constraint logic to PHP?

On Fri, Jun 10, 2016 at 2:23 PM, Ken Tanzer wrote: > On Fri, Jun 10, 2016 at 1:47 PM, Steve Atkins wrote: > >> > You could look at one of the existing SQL parsers implemented in PHP, and >> use those to parse the constraint to a tree from which you

Re: [GENERAL] Converting Postgres SQL constraint logic to PHP?

On Fri, Jun 10, 2016 at 1:54 PM, rob stone wrote: > > Hi Ken, > > Would this be static or dynamic? > For example, if you altered a column to become defined as NOT NULL, > say, when you build the form used to maintain that table you'd like to > have a "required" attribute

Re: [GENERAL] Converting Postgres SQL constraint logic to PHP?

On Fri, Jun 10, 2016 at 1:47 PM, Steve Atkins wrote: > > You could name the check constraints, catch the errors and use a > client-side mapping between constraint name and a friendly error message > for display in the web interface. > > This seems plausible, but not ideal. I

Re: [GENERAL] Converting Postgres SQL constraint logic to PHP?

On Fri, 2016-06-10 at 13:01 -0700, Ken Tanzer wrote: > Hi.  I was hoping this list might be able to offer some > help/advice/suggestions/opinions about feasibility for something I > want to implement, namely converting Postgres constraints into PHP > logic.  Here's the context and explanation: >

Re: [GENERAL] Converting Postgres SQL constraint logic to PHP?

> On Jun 10, 2016, at 1:01 PM, Ken Tanzer wrote: > > Hi. I was hoping this list might be able to offer some > help/advice/suggestions/opinions about feasibility for something I want to > implement, namely converting Postgres constraints into PHP logic. Here's the >

[GENERAL] Converting Postgres SQL constraint logic to PHP?

Hi. I was hoping this list might be able to offer some help/advice/suggestions/opinions about feasibility for something I want to implement, namely converting Postgres constraints into PHP logic. Here's the context and explanation: I work on a PHP web app using Postgres. When possible, we try

Re: [GENERAL] Partitioned postgres tables don't need update trigger??

Perfect! Thanks for the response! Just wanted to make sure I wasn't missing anything. -- View this message in context: http://postgresql.nabble.com/Partitioned-postgres-tables-don-t-need-update-trigger-tp5906403p5906415.html Sent from the PostgreSQL - general mailing list archive at

Re: [GENERAL] Partitioned postgres tables don't need update trigger??

On Fri, Jun 3, 2016 at 5:03 PM, rverghese wrote: > I am working with partitioned tables. I have partitioned based on date and > I have the INSERT trigger in place, I don't have an Update or Delete > Trigger but both updates and deletes against the master table work >

[GENERAL] Partitioned postgres tables don't need update trigger??

I am working with partitioned tables. I have partitioned based on date and I have the INSERT trigger in place, I don't have an Update or Delete Trigger but both updates and deletes against the master table work correctly. I am not sure how these are working without triggers. Any insight? So, this

Re: [GENERAL] Connections - Postgres 9.2

On 17 May 2016 at 22:24, Sridhar N Bamandlapally wrote: > Hi > > I control this way > > if "state_change" is from longtime and "state" is idle then I use > > function: > *pg_terminate_backend ( integer ) * ==> return TRUE if > killed-successful else FALSE > > example: >

Re: [GENERAL] Connections - Postgres 9.2

Hi I control this way if "state_change" is from longtime and "state" is idle then I use function: *pg_terminate_backend ( integer ) * ==> return TRUE if killed-successful else FALSE example: # select pg_terminate_backend ( pid ) from pg_stat_activity where state='idle' and state_change <

Re: [GENERAL] Connections - Postgres 9.2

On 05/16/2016 02:25 PM, John R Pierce wrote: On 5/16/2016 2:11 PM, Adrian Klaver wrote: Yes a connection consumes resources. an idle connection consumes some memory, a process context, and a network socket. its not using CPU or disk IO. True, but the existence of poolers says that can be

Re: [GENERAL] Connections - Postgres 9.2

On 5/16/2016 2:11 PM, Adrian Klaver wrote: Yes a connection consumes resources. an idle connection consumes some memory, a process context, and a network socket. its not using CPU or disk IO. True, but the existence of poolers says that can be an issue. I note that MRTG style graph

Re: [GENERAL] Connections - Postgres 9.2

On 05/16/2016 02:00 PM, John R Pierce wrote: On 5/16/2016 1:55 PM, Adrian Klaver wrote: Would the pool connection solve that IDLE connections? But more important than that, are the IDLE connections using the machine's resources ? Yes a connection consumes resources. an idle connection

Re: [GENERAL] Connections - Postgres 9.2

On 17 May 2016 at 08:56, Venkata Balaji N wrote: > > On Tue, May 17, 2016 at 6:28 AM, Lucas Possamai > wrote: > >> hmm.. thanks for all the answers guys... >> >> >> One more question: Those IDLE connections.. are using the server's >> resources? >> To

Re: [GENERAL] Connections - Postgres 9.2

On 5/16/2016 1:55 PM, Adrian Klaver wrote: Would the pool connection solve that IDLE connections? But more important than that, are the IDLE connections using the machine's resources ? Yes a connection consumes resources. an idle connection consumes some memory, a process context, and a

Re: [GENERAL] Connections - Postgres 9.2

On Tue, May 17, 2016 at 6:28 AM, Lucas Possamai wrote: > hmm.. thanks for all the answers guys... > > > One more question: Those IDLE connections.. are using the server's > resources? > To solve that problem I would need a Pool connection, right? > > Would the pool

Re: [GENERAL] Connections - Postgres 9.2

On 05/16/2016 01:28 PM, Lucas Possamai wrote: hmm.. thanks for all the answers guys... One more question: Those IDLE connections.. are using the server's resources? To solve that problem I would need a Pool connection, right? Yes and no. If your application/clients are generating connections

Re: [GENERAL] Connections - Postgres 9.2

hmm.. thanks for all the answers guys... One more question: Those IDLE connections.. are using the server's resources? To solve that problem I would need a Pool connection, right? Would the pool connection solve that IDLE connections? But more important than that, are the IDLE connections using

Re: [GENERAL] Connections - Postgres 9.2

On 05/16/2016 09:56 AM, Charles Clavadetscher wrote: Hello On 16.05.2016, at 18:32, Francisco Olarte > wrote: Hi Lucas On Mon, May 16, 2016 at 4:10 AM, Lucas Possamai > wrote:

Re: [GENERAL] Connections - Postgres 9.2

Charles: On Mon, May 16, 2016 at 6:56 PM, Charles Clavadetscher wrote: > There really is a state 'Idle in transaction'? Good to learn. Again, IIRC, it was there in the graph legend, orange was Idle, yellow was Idle in transaction ( not in the data, just in the

Re: [GENERAL] Connections - Postgres 9.2

Hello > On 16.05.2016, at 18:32, Francisco Olarte wrote: > > Hi Lucas > >> On Mon, May 16, 2016 at 4:10 AM, Lucas Possamai wrote: >> >> Those IDLE connections, might be because the user/application didn't commit >> the transaction? > > ​IIRC

Re: [GENERAL] Connections - Postgres 9.2

Hi Lucas On Mon, May 16, 2016 at 4:10 AM, Lucas Possamai wrote: > > Those IDLE connections, might be because the user/application didn't > commit the transaction? > ​IIRC Those would be 'Idle in transaction' ( which are normally bad if numerous, unless your app has a

Re: [GENERAL] Connections - Postgres 9.2

Hello > On 16.05.2016, at 04:10, Lucas Possamai wrote: > > Hi guys, > > > > Those IDLE connections, might be because the user/application didn't commit > the transaction? I think that idle means that a client is connected but is doing nothing. Possibly It includes

Re: [GENERAL] understanding postgres backend process memory usage

Day, David Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] understanding postgres backend process memory usage Hi David, How many different table/objects do you read from and do you use bind variables? Each postmaster process keeps internal dictionary on objects and queries ran - If you h

Re: [GENERAL] Re: Postgres 9.4.4/9.4.6: plpython2/3 intallation issues on a Windows 7 machine

On 03/31/2016 02:53 AM, margrit drescher wrote: I originally used the 9.4.6 version on http://www.enterprisedb.com/products-services-training/pgdownload#windows for 64-bit windows and loaded the language pack recommended in the readme file. Did you do this?: If you are using Windows 64, you

[GENERAL] Re: Postgres 9.4.4/9.4.6: plpython2/3 intallation issues on a Windows 7 machine

I originally used the 9.4.6 version on http://www.enterprisedb.com/products-services-training/pgdownload#windows for 64-bit windows and loaded the language pack recommended in the readme file. On 31 March 2016 at 11:25, Alex Ignatov-2 [via PostgreSQL] < ml-node+s1045698n5896174...@n5.nabble.com>

[GENERAL] regarding postgres feedback

Hi Sir i am very happy to work on PostgreSQL.Super fast response only from postgres team regarding i asked any question related to postgres regards mahesh

Re: [GENERAL] bloated postgres data folder, clean up

​Hey Julien, thanks for the original query ! ​ There was a slight mistake in the query, it was comparing the file name with pg_class.relfilenode. It is not safe in some case (see doc : "caution" in here ) , so better use the

Re: [GENERAL] bloated postgres data folder, clean up

> > __ __ > > *Johnny Morano | Principal Systems Engineer* > > __ __ > > PAY.ON GmbH | AN ACI WORLDWIDE COMPANY | WWW.PAYON.COM > <http://www.payon.com/> > > Jakob-Haringer-Str. 1 | 5020 Salzburg | Aust

Re: [GENERAL] bloated postgres data folder, clean up

PAY.ON GmbH | AN ACI WORLDWIDE COMPANY | WWW.PAYON.COM > <http://www.payon.com/> > > Jakob-Haringer-Str. 1 | 5020 Salzburg | Austria > > > > This email message and any attachments may contain confidential, > proprietary or non-public information. This inf

Re: [GENERAL] bloated postgres data folder, clean up

Rémi Cura [mailto:remi.c...@gmail.com] Sent: Mittwoch, 2. März 2016 17:49 To: Johnny Morano Cc: Alvaro Herrera; PostgreSQL General Subject: Re: [GENERAL] bloated postgres data folder, clean up Hey, this is quite the *opposite*. The function find files in the postgres database folder that are not

Re: [GENERAL] bloated postgres data folder, clean up

s arising as a result of > any virus being passed on or arising from any alteration of this message by > a third party. PAY.ON may monitor e-mails sent to and from PAY.ON. > > > > > > > > > > *From:* pgsql-general-ow...@postgresql.org [mailto: > pgsql-general-ow..

Re: [GENERAL] bloated postgres data folder, clean up

o Herrera Cc: PostgreSQL General Subject: Re: [GENERAL] bloated postgres data folder, clean up Would gladly do it, but still this "wiki cooloff" stuff, can't create a page Cheers, Rémi-C 2016-02-29 20:44 GMT+01:00 Alvaro Herrera <alvhe...@2ndquadrant.com<mailto:alvhe...@2ndquadrant

Re: [GENERAL] bloated postgres data folder, clean up

Would gladly do it, but still this "wiki cooloff" stuff, can't create a page Cheers, Rémi-C 2016-02-29 20:44 GMT+01:00 Alvaro Herrera : > Rémi Cura wrote: > > Hey dear list, > > after a fex years of experiments and crash, > > I ended up with a grossly bloated postgres

Re: [GENERAL] bloated postgres data folder, clean up

Rémi Cura wrote: > Hey dear list, > after a fex years of experiments and crash, > I ended up with a grossly bloated postgres folder. > I had about 8 Go of useless files. Would you add a new page to the wiki with this? https://wiki.postgresql.org/wiki/Category:Administrative_Snippets -- Álvaro

Re: [GENERAL] bloated postgres data folder, clean up

> Hope this may be useful Thanks for sharing! Peter -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

[GENERAL] bloated postgres data folder, clean up

Hey dear list, after a fex years of experiments and crash, I ended up with a grossly bloated postgres folder. I had about 8 Go of useless files. All is in a virtualbox, so I'm sure to be able to reproduce exactly, and fried my postgres folder a couple of time before getting it right. Julien

Re: [GENERAL] Why Postgres use a little memory on Windows.

On 02/20/2016 10:39 AM, Francisco Olarte wrote: On Sat, Feb 20, 2016 at 7:13 PM, Adrian Klaver wrote: . FROM sym_data d INNER JOIN sym_data_gap g ON g.status = 'GP' AND d.data_id BETWEEN g.start_id AND g.end_id . The thing that stands out to

Re: [GENERAL] Why Postgres use a little memory on Windows.

On Sat, Feb 20, 2016 at 7:37 PM, Tom Lane wrote: > It looks like the bitmap heap scan generally returns exactly one row for > each outer row, which makes me wonder if the BETWEEN couldn't be replaced > with some sort of equality. Mm, I'm not good reading explains, but that

Re: [GENERAL] Why Postgres use a little memory on Windows.

On Sat, Feb 20, 2016 at 7:13 PM, Adrian Klaver wrote: . > FROM > sym_data d INNER JOIN sym_data_gap g ON g.status = 'GP' > AND d.data_id BETWEEN g.start_id > AND g.end_id . > The thing that stands out to me is that I do not see that sym_data and >

Re: [GENERAL] Why Postgres use a little memory on Windows.

Adrian Klaver writes: > Took liberty of reformatting the above here: > ... > FROM > sym_data d INNER JOIN sym_data_gap g ON g.status = 'GP' > AND d.data_id BETWEEN g.start_id > AND g.end_id > WHERE > d.channel_id = 'sale_transaction' > ORDER BY >

Re: [GENERAL] Why Postgres use a little memory on Windows.

On 02/20/2016 08:46 AM, tuanhoanganh wrote: Hello I have a bad query on PostgreSQL 9.0.23 - 64bit - Windows 2012 R2 - 48GB Ram explain analyze select d.data_id, d.table_name, d.event_type, d.row_data, d.pk_data, d.old_data, d.create_time, d.trigger_hist_id, d.channel_id, d.transaction_id,

[GENERAL] Why Postgres use a little memory on Windows.

Hello I have a bad query on PostgreSQL 9.0.23 - 64bit - Windows 2012 R2 - 48GB Ram explain analyze select d.data_id, d.table_name, d.event_type, d.row_data, d.pk_data, d.old_data, d.create_time, d.trigger_hist_id, d.channel_id, d.transaction_id, d.source_node_id, d.external_data, '' from

Re: [GENERAL] Charlotte Postgres User Group

Definitely putting this on my calendar. I have not been aware of other PostgreSQL users here - would love to meet some other users. Don On Wed, Feb 17, 2016 at 10:39 AM, Boyan Botev wrote: > If you live near or around Charlotte, please join us for the inaugural > meeting of

[GENERAL] Charlotte Postgres User Group

If you live near or around Charlotte, please join us for the inaugural meeting of the Charlotte PUG on March 1, followed by a second meeting on April 11 featuring Bruce Momjian. More information about the two events can be found here: http://www.meetup.com/Charlotte-PostgreSQL-User-Group Also if

Re: [GENERAL] Auotmated postgres failover

Le Thu, 21 Jan 2016 11:34:18 -0800, John R Pierce a écrit : > On 1/21/2016 11:07 AM, jwienc...@comcast.net wrote: > > > > > > I'm looking for a tool to automate PostgreSQL cluster management > > failover in the event the master database were to become unavailable. > >

Re: [GENERAL] Auotmated postgres failover

On 1/21/2016 11:07 AM, jwienc...@comcast.net wrote: I'm looking for a tool to automate PostgreSQL cluster management failover in the event the master database were to become unavailable. Currently are manually issuing a "pg_ctl promote" once we become aware that the master database has

  1   2   3   4   5   6   7   8   9   10   >