[GENERAL] Query Questions - PostgreSQL

So.. I have a Query that is taking too long to complete. OLD QUERY: SELECT file.inode_idAS file_id, file.parent_inode_id AS file_group, file.relative_path AS file_type, file.file_data AS file_binary, file.node_full_path AS file_name, file.last_modified AS

Re: [GENERAL] WIP: CoC V5

The small problem with your version, Joshua, is that the appropriate action is not specified. Sorry to jump in in the middle. I have not read the comments fully. Elein Mustain el...@varlena.com > On Jan 12, 2016, at 2:56 PM, Joshua D. Drake wrote: > >> On

Re: [GENERAL] WIP: CoC V5

Elein writes: > The small problem with your version, Joshua, is that the appropriate action > is not specified. I think at this point we're just trying to agree on a statement as to what actions are acceptable or not. After that we can get into what is the enforcement

Re: [GENERAL] WIP: CoC V5

Still trying the Danish "Make Love not Codes" approach (Love being the plural of the Danish Lov meaning law). 1. The CoC is to provide community guidelines for creating and enforcing a safe, respectful, productive, and collaborative place for any person who is willing to contribute in a safe,

Re: [GENERAL] WIP: CoC V5

On 01/12/2016 07:10 PM, Tom Lane wrote: Kevin Grittner writes: I'm not the greatest word-smith, but I'll attempt to rework Josh's draft to something that seems more "natural" to me. Minor (or not?) comment: * To maintain a safe, respectful, productive and collaborative

[GENERAL] Unable to build python extension with PGXS

Attempting to build a python extension, I'm getting: Undefined symbols for architecture x86_64: "_PyErr_Clear", referenced from: _PLyNdarray_FromDatum in pg_ndarray.o _PLyObject_To_ndarray in pg_ndarray.o "_PyImport_ImportModule", referenced from: _PLyNdarray_FromDatum in

Re: [GENERAL] WIP: CoC V5

Kevin Grittner writes: > I'm not the greatest word-smith, but I'll attempt to rework Josh's > draft to something that seems more "natural" to me. Minor (or not?) comment: > * To maintain a safe, respectful, productive and collaborative > environment all participants must

Re: [GENERAL] WIP: CoC V5

On 01/12/2016 07:04 PM, Tom Lane wrote: "Joshua D. Drake" writes: On 01/12/2016 02:43 PM, Kevin Grittner wrote: To me, this reads more like the document itself. I hope I have done justice to Josh's points as well as Tom's, although I would bet there are a number of

Re: [GENERAL] WIP: CoC V5

On 01/12/2016 06:41 PM, Elein wrote: The small problem with your version, Joshua, is that the appropriate action is not specified. Sorry to jump in in the middle. I have not read the comments fully. It is all good Elein. The lack of appropriate action is purposeful. The idea is that we

Re: [GENERAL] WIP: CoC V5

On 01/12/2016 06:55 PM, Tom Lane wrote: Elein writes: The small problem with your version, Joshua, is that the appropriate action is not specified. I think at this point we're just trying to agree on a statement as to what actions are acceptable or not. After that we can

[GENERAL] Data Packaging/Data Unpacking

Greetings, I have matching couple of security requirements, speaking about preserving data confidentiality and integrity in PostgreSQL DB during packaging for transmission / unpacking from transmission. Important: let's assume data at rest is encrypted using EFS and data at transit is encrypted

Re: [GENERAL] Code of Conduct: Is it time?

On Tue, Jan 12, 2016 at 3:21 PM, James Keener wrote: > This line has already been substantially changes. Can we keep discussion > of the language of the WIP in the thread meant for it? This way people > don't waste time discussing language which no longer exists. > I think

Re: [GENERAL] Moving a large DB (> 500GB) to another DB with different locale

On Tue, Jan 12, 2016 at 4:09 PM, Andreas Joseph Krogh wrote: > På tirsdag 12. januar 2016 kl. 22:56:56, skrev John R Pierce < > pie...@hogranch.com>: > > On 1/12/2016 1:20 PM, Andreas Joseph Krogh wrote: > > I'm moving a > 500GB DB to another server which is initdb'ed with a

Re: [GENERAL] Moving a large DB (> 500GB) to another DB with different locale

On Tue, Jan 12, 2016 at 4:20 PM, Andreas Joseph Krogh wrote: > I'm moving a > 500GB DB to another server which is initdb'ed with a > different locale (nb_NO.UTF-8 to get correct collation when ORDER BY). > Is there another option than pg_dump/restore for doing this? > I

Re: [GENERAL] WIP: CoC V5

On Tue, 12 Jan 2016 22:10:43 -0500 Tom Lane wrote: > Kevin Grittner writes: > > I'm not the greatest word-smith, but I'll attempt to rework Josh's > > draft to something that seems more "natural" to me. > > Minor (or not?) comment: > > > * To maintain a

Re: [GENERAL] WIP: CoC V5

"Joshua D. Drake" writes: > On 01/12/2016 02:43 PM, Kevin Grittner wrote: >> To me, this reads more like the document itself. I hope I have >> done justice to Josh's points as well as Tom's, although I would >> bet there are a number of people on the list that can improve

Re: [GENERAL] Code of Conduct: Is it time?

On Tue, Jan 12, 2016 at 9:16 AM, Regina Obe wrote: > Chris, > > > > The first part up to (I is fine), but part II and below reads more like a > Core Contributor riot act you force all the main contributor's to read > before you bless them with water and give them keys to commit

Re: [GENERAL] PostgreSQL upgrade 9.3.4 -> 9.3.10

Hello: On Tue, Jan 12, 2016 at 10:28 AM, Dev Kumkar wrote: > I want to upgrade my database from version 9.3.4 to 9.3.10. > > For this task, do I need to upgrade database using pg_upgrade utility? > http://www.postgresql.org/docs/9.3/static/pgupgrade.html No, that is a

Re: [GENERAL] PostgreSQL upgrade 9.3.4 -> 9.3.10

On 1/12/2016 1:28 AM, Dev Kumkar wrote: I want to upgrade my database from version 9.3.4 to 9.3.10. For this task, do I need to upgrade database using pg_upgrade utility? http://www.postgresql.org/docs/9.3/static/pgupgrade.html From the details it looks like for minor version upgrade

Re: [GENERAL] Code of Conduct: Is it time?

A couple thoughts rather late to the discussion from a more international perspective. I remember a lecture I saw by a comparative law professor (the lecture was about why many Danes are unhappy with the EU pressures on their tradition of law and the general lack of subsidiarity in the EU) who

Re: [GENERAL] Code of Conduct: Is it time?

Chris, The first part up to (I is fine), but part II and below reads more like a Core Contributor riot act you force all the main contributor's to read before you bless them with water and give them keys to commit stuff to your code base. Like our committer guidelines --

Re: [GENERAL] Giving error for function

Hello > -Original Message- > From: pgsql-general-ow...@postgresql.org > [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Sachin Srivastava > Sent: Dienstag, 12. Januar 2016 08:40 > To: pgsql-general@postgresql.org >> PG-General Mailing List > >

Re: [GENERAL] PostgreSQL upgrade 9.3.4 -> 9.3.10

Dev Kumkar wrote: > Hello, > > > I want to upgrade my database from version 9.3.4 to 9.3.10. > > For this task, do I need to upgrade database using pg_upgrade utility? > http://www.postgresql.org/docs/9.3/static/pgupgrade.html No. > Can someone please provide more

Re: [GENERAL] WIP: CoC V2

Josh, > tl;dr; > * Modified #2 to be less harsh. > * Modified #3 with TGL and James comments > * Did not remove examples as I believe they are vital to the success > I saw Regina's post, I believe it is good for context but I also believe that > something concise and to the point is the better

Re: [GENERAL] PostgreSQL upgrade 9.3.4 -> 9.3.10

On Tue, Jan 12, 2016 at 10:28 AM, Dev Kumkar wrote: > > Hello, > > > I want to upgrade my database from version 9.3.4 to 9.3.10. > > For this task, do I need to upgrade database using pg_upgrade utility? > http://www.postgresql.org/docs/9.3/static/pgupgrade.html > > >

Re: [GENERAL] WIP: CoC V3

Sorry. I just saw the reference to this in the related thread. On Jan 11, 2016 7:01 PM, "Andy Chambers" wrote: > Any reason not to just adopt the contributor covenant? > > http://contributor-covenant.org/ > tl;dr; > > * Removed #6 (Social Justice) > > PostgreSQL Global

Re: [GENERAL] Code of Conduct: Is it time?

On Jan 12, 2016 9:48 AM, "Regina Obe" wrote: >> >> Chris, >> >> >> For a Coc – I think it should be light, but make it clear that we do not tolerate strangers coming into our group and demanding us to accept their code, cause we want to be welcoming and show we have at least 15% of

Re: [GENERAL] Code of Conduct: Is it time?

On 12 January 2016 at 09:25, Chris Travers wrote: > One of the dangers of a CoC is that there are many potential issues which > may or may not become real problems. I think if we try to be clear on all > of them, then we risk creating codes instead of a general

Re: [GENERAL] Code of Conduct: Is it time?

Chris, >> For a Coc – I think it should be light, but make it clear that we do not >> tolerate strangers coming into our group and demanding us to accept their >> code, cause we want to be welcoming and show we have at least 15% of code >> contributions from women. > One of the dangers of

[GENERAL] PostgreSQL upgrade 9.3.4 -> 9.3.10

Hello, I want to upgrade my database from version 9.3.4 to 9.3.10. For this task, do I need to upgrade database using pg_upgrade utility? http://www.postgresql.org/docs/9.3/static/pgupgrade.html >From the details it looks like for minor version upgrade pg_upgrade utility is not required.

Re: [GENERAL] Offline Tablespaces and Partial Restore

Thank you for your response David. Yea, we are considering doing all the function calls and access to tables with dblink and see how bad this would hurt performance. It will be tough to explain this to the SQL Server guys. Maybe there is another approach to deal with this kind of environment?

Re: [GENERAL] Code of Conduct: Is it time?

On Mon, Jan 11, 2016 at 6:55 PM, Steve Litt wrote: > All because somebody just *had* to personally insult someone else, > repeatedly, and nobody thought that was a bad thing, and when the > recipient finally objected, the objection was chalked up to him or her > valuing

Re: [GENERAL] Code of Conduct: Is it time?

> On Jan 12, 2016, at 7:50 AM, Vick Khera wrote: > > On Mon, Jan 11, 2016 at 6:55 PM, Steve Litt wrote: >> All because somebody just *had* to personally insult someone else, >> repeatedly, and nobody thought that was a bad thing, and when the >>

Re: [GENERAL] WIP: CoC

>> That has nothing to do with the Code of Conduct, though. >> The community accepting Tom saying "no" to Feature X is >> vastly different than the community not calling Tom out >> for being mean. >> The CoC is about the later situation and not the prior; >> and the community should call Tom out.

Re: [GENERAL] Offline Tablespaces and Partial Restore

On 1/12/16 6:02 AM, Pedro França wrote: > Yea, we are considering doing all the function calls and access to > tables with dblink and see how bad this would hurt performance. It will > be tough to explain this to the SQL Server guys. You should consider using the Postgres FDW

Re: [GENERAL] PostgreSQL upgrade 9.3.4 -> 9.3.10

On Tue, Jan 12, 2016 at 3:25 PM, John R Pierce wrote: > On 1/12/2016 1:28 AM, Dev Kumkar wrote: > > > I want to upgrade my database from version 9.3.4 to 9.3.10. > > For this task, do I need to upgrade database using pg_upgrade utility? >

Re: [GENERAL] Code of Conduct: Is it time?

> On 12 January 2016 at 09:25, Chris Travers wrote: >> One of the dangers of a CoC is that there are many potential issues >> which may or may not become real problems. I think if we try to be >> clear on all of them, then we risk creating codes instead of a general

Re: [GENERAL] WIP: CoC

> If the attacker goes public, we point people at the exchange that happened > where Tom has presumably already discussed the reasons that the > patch/feature/ isn't being accepted. If someone wanted to out someone, they would study them carefully. They would find Tom's buttons and push

Re: [GENERAL] WIP: CoC

Wow. I mean actually wow. So many things. Just so many. You still haven't explained why core contributors need to be treated like special snowflakes. If someone acts inappropriately then they should be told so, regardless of status. Why should we protect anyone in the wrong? Moreover, your

Re: [GENERAL] Code of Conduct: Is it time?

This line has already been substantially changes. Can we keep discussion of the language of the WIP in the thread meant for it? This way people don't waste time discussing language which no longer exists. Jim On January 12, 2016 9:17:55 AM EST, Neil Tiffin wrote: > >> On

Re: [GENERAL] postgres user with password read-only user without?

On 01/12/2016 09:41 AM, Ted Toth wrote: Is there a way to configure authentication so that some users require a password and other users don't? Yes, see: http://www.postgresql.org/docs/9.4/interactive/auth-pg-hba-conf.html "user Specifies which database user name(s) this record matches.

Re: [GENERAL] postgres user with password read-only user without?

On Tue, Jan 12, 2016 at 10:41 AM, Ted Toth wrote: > Is there a way to configure authentication so that some users require > a password and other users don't? > ​Yes. http://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html David J.​

Re: [GENERAL] WIP: CoC

On 01/12/2016 08:17 AM, Neil Tiffin wrote: On Jan 12, 2016, at 12:20 AM, Tom Lane wrote: [ just a few comments on specific points ] "Greg Sabino Mullane" writes: 2. The CoC is not about being offended. The act of being offended is purely a recipient

Re: [GENERAL] WIP: CoC V4

On Tue, Jan 12, 2016 at 11:50 AM, Joshua D. Drake wrote: > Tl;dr; > > * Removed specific examples and reworded #3 to be more concise > > PostgreSQL Global Development Group (PGDG) Code of Conduct (CoC): > > 1. The CoC is to provide community guidelines for creating and

[GENERAL] Moving a large DB (> 500GB) to another DB with different locale

Hi all.   I'm moving a > 500GB DB to another server which is initdb'ed with a different locale (nb_NO.UTF-8 to get correct collation when ORDER BY). Is there another option than pg_dump/restore for doing this?   Thanks.   -- Andreas Joseph Krogh CTO / Partner - Visena AS Mobile: +47 909 56 963

Re: [GENERAL] Slow Query - PostgreSQL 9.2

UPDATED: Index created:create index concurrently inode_segments_st_ino_target_pidx on gorfs.inode_segments (st_ino desc, st_ino_target desc) where nfs_migration_date is null; NEW EXPLAIN ANALYZE:http://explain.depesz.com/s/Swu I also am able to create a temporary table to store migrations, which

Re: [GENERAL] WIP: CoC V4

On 01/12/2016 12:16 PM, Oleg Bartunov wrote: 4. Any sustained disruption of the collaborative space (mailing lists, IRC etc..) or other PostgreSQL events shall be construed as a violation of the CoC and appropriate action will be taken by the CoC committee. Then we need to

Re: [GENERAL] Moving a large DB (> 500GB) to another DB with different locale

On 1/12/2016 1:20 PM, Andreas Joseph Krogh wrote: I'm moving a > 500GB DB to another server which is initdb'ed with a different locale (nb_NO.UTF-8 to get correct collation when ORDER BY). Is there another option than pg_dump/restore for doing this? nope, because the text data has to be

Re: [GENERAL] WIP: CoC V5

tl;dr; * Moved #2 to #3 and #3 to #2 * Added wording for assuming positive intent to #2 PostgreSQL Global Development Group (PGDG) Code of Conduct (CoC): 1. The CoC is to provide community guidelines for creating and enforcing a safe, respectful, productive, and collaborative place for any

Re: [GENERAL] Moving a large DB (> 500GB) to another DB with different locale

På tirsdag 12. januar 2016 kl. 22:56:56, skrev John R Pierce < pie...@hogranch.com >: On 1/12/2016 1:20 PM, Andreas Joseph Krogh wrote: > I'm moving a > 500GB DB to another server which is initdb'ed with a > different locale (nb_NO.UTF-8 to get correct collation when

Re: [GENERAL] Code of Conduct: Is it time?

On 05/01/2016 18:47, Joshua D. Drake wrote: Hello, I had a hard time writing this email. I think Code of Conducts are non-essential, a waste of respectful people's time and frankly if you are going to be a jerk, our community will call you out on it. Unfortunately a lot of people don't agree

German, was: Re: [GENERAL] Code of Conduct: Is it time?

> To add to that, non-native speakers sometimes make mistakes that set > it off. I remember an embarrassing case where I thought the word > "gross" came from the German "Grosshaft", which means quite the > opposite (great, fabulous), and responded to a new idea on a list with > a heartily meant

Re: [GENERAL] WIP: CoC V4

On Tue, Jan 12, 2016 at 7:50 PM, Joshua D. Drake wrote: > Tl;dr; > > * Removed specific examples and reworded #3 to be more concise > > PostgreSQL Global Development Group (PGDG) Code of Conduct (CoC): > > 1. The CoC is to provide community guidelines for creating and

Re: [GENERAL] 9.4 -> 9.5 upgrade problem when both python2 and python3 present

On Mon, Jan 11, 2016 at 06:23:06PM -0500, Tom Lane wrote: > Date: Mon, 11 Jan 2016 18:23:06 -0500 > From: Tom Lane > To: Paul Jones > cc: pgsql-general@postgresql.org > Subject: Re: [GENERAL] 9.4 -> 9.5 upgrade problem when both python2 and > python3 present

Re: [GENERAL] Code of Conduct: Is it time?

On 1/12/2016 5:42 AM, Regina Obe wrote: a) Some people won't feel welcome if they don't see one b) Malicious people will spread rumors about our project for not having one , but if we have one, it has to protect us from them working within the rules, but pushing everyone's buttons. c) and if

Re: [GENERAL] plv8 binaries for PostgreSQL 9.5 on Windows

On 01/11/2016 05:50 PM, Igal @ Lucee.org wrote: Where can I find binaries for plv8 for PostgreSQL 9.5 for Windows? The only Windows binaries I could find where for 9.4, here:

Re: [GENERAL] PostgreSQL upgrade 9.3.4 -> 9.3.10

On 01/12/2016 01:37 AM, Shulgin, Oleksandr wrote: On Tue, Jan 12, 2016 at 10:28 AM, Dev Kumkar > wrote: > > Hello, > > > I want to upgrade my database from version 9.3.4 to 9.3.10. > > For this task, do I need to upgrade database

Re: [GENERAL] WIP: CoC

James, I was describing a real live scenario. I was describing what happened to Linus Torvalds. Only part was he hasn't left yet. He's stood his ground and ignored the tyrants. Remember I'm on the side of not having a Coc. I have trouble debating things I don't believe in. I was

Re: [GENERAL] WIP: CoC

> everyone should be excellent to one another, as defined in a general CoC I think CoralineAda has debated extensively why being excellent is not sufficient. https://modelviewculture.com/pieces/codes-of-conduct-when-being-excellent-is-not-enough I personally don't have the patience to

Re: [GENERAL] WIP: CoC

> > > https://modelviewculture.com/pieces/codes-of-conduct-when-being-excellent-is-not-enough > That post seems to discuss why a written CoC is needed (as opposed to an unwritten "act professional" one). I don't believe it applies to my comment.

Re: [GENERAL] Giving error for function

Sachin Srivastava writes: > I am getting the below error while I am running the below function > "add_po_doc_hist", for "c_company" cursor, please suggest what is wrong > with code. > ERROR: relation "c_company" does not exist > CONTEXT: compilation of PL/pgSQL function

Re: [GENERAL] Text parameter is treated as sql query in postgresql function

On 01/11/2016 11:47 PM, Yash Gajbhiye wrote: I am using postgres crosstab() function to create a table. My first dynamic query function (dynamic_crosstab) creates a sql select statement containing crosstab(), and then this select statement gives the final result on execution. /*dynamic_crosstab

Re: [GENERAL] WIP: CoC

On Tue, 2016-01-12 at 09:07 -0500, Regina Obe wrote: > > If the attacker goes public, we point people at the exchange that happened > > where Tom has presumably already discussed the reasons that the > > patch/feature/ isn't being accepted. > > If someone wanted to out someone, they would

Re: [GENERAL] WIP: CoC

Bret, Thanks. That made me feel much better. I was about to walk out the door never to use PostgreSQL lists again because I thought Josh was an insensitive jerk flapping his wings about "respectful, collaborative" , and I certainly violated the new "respectful" mantra buy calling his

Re: [GENERAL] Moving a large DB (> 500GB) to another DB with different locale

På tirsdag 12. januar 2016 kl. 23:28:55, skrev Tom Lane >: Andreas Joseph Krogh writes: > P�� tirsdag 12. januar 2016 kl. 22:56:56, skrev John R Pierce < > pie...@hogranch.com >: >> On 1/12/2016

Re: [GENERAL] Moving a large DB (> 500GB) to another DB with different locale

Andreas Joseph Krogh writes: > Are you saying that I don't have to re-initdb and can just change collation > somehow? If so, how? Collation is really pretty much a per-index property these days; the DB-level setting only provides a default. You could imagine some process

Re: [GENERAL] Moving a large DB (> 500GB) to another DB with different locale

På tirsdag 12. januar 2016 kl. 23:49:24, skrev Tom Lane >: Andreas Joseph Krogh writes: > Are you saying that I don't have to re-initdb and can just change collation > somehow? If so, how? Collation is really pretty much a

Re: [GENERAL] WIP: CoC V5

On 01/12/2016 02:43 PM, Kevin Grittner wrote: I think that this is fairly close to something that would make sense, but there is sort of a weirdness in the CoC referring to itself in the 3rd person. It sound more like an argument for *having* a CoC than the document itself. I'm not the

Re: [GENERAL] Moving a large DB (> 500GB) to another DB with different locale

Andreas Joseph Krogh writes: > What about ORDER BY on columns without an index, would they sort correctly? Sorting is sorting, it'll just use whatever collation is specified or implied. regards, tom lane -- Sent via pgsql-general mailing list

Re: [GENERAL] Moving a large DB (> 500GB) to another DB with different locale

På onsdag 13. januar 2016 kl. 00:03:18, skrev Tom Lane >: Andreas Joseph Krogh writes: > What about ORDER BY on columns without an index, would they sort correctly? Sorting is sorting, it'll just use whatever collation is

Re: [GENERAL] WIP: CoC V5

I think that this is fairly close to something that would make sense, but there is sort of a weirdness in the CoC referring to itself in the 3rd person. It sound more like an argument for *having* a CoC than the document itself. I'm not the greatest word-smith, but I'll attempt to rework Josh's

Re: [GENERAL] WIP: CoC V5

On 01/12/2016 02:43 PM, Kevin Grittner wrote: I guess I should scroll all the way down. :P To me, this reads more like the document itself. I hope I have done justice to Josh's points as well as Tom's, although I would bet there are a number of people on the list that can improve on my

Re: [GENERAL] Text parameter is treated as sql query in postgresql function

Hello Adrian, Thank you for your response. Sorry about the typos in the previous post. I will try to explain myself more clearly. This is my first function to create a dynamic query and it is as follows: CREATE OR REPLACE FUNCTION dynamic_crosstab( source_sql text, category_sql text,

Re: [GENERAL] Text parameter is treated as sql query in postgresql function

On 12/01/2016 17:07, Yash Gajbhiye wrote: > Hello Adrian, > > Thank you for your response. Sorry about the typos in the previous post. > > I will try to explain myself more clearly. > > This is my first function to create a dynamic query and it is as follows: > > CREATE OR REPLACE FUNCTION

Re: [GENERAL] WIP: CoC V4

Tl;dr; * Removed specific examples and reworded #3 to be more concise PostgreSQL Global Development Group (PGDG) Code of Conduct (CoC): 1. The CoC is to provide community guidelines for creating and enforcing a safe, respectful, productive, and collaborative place for any person who is

Re: [GENERAL] WIP: CoC

> On Jan 12, 2016, at 12:20 AM, Tom Lane wrote: > > [ just a few comments on specific points ] > > "Greg Sabino Mullane" writes: >>> 2. The CoC is not about being offended. The act of being offended is >>> purely a recipient response and usually the

Re: [GENERAL] Text parameter is treated as sql query in postgresql function

On 01/12/2016 09:07 AM, Yash Gajbhiye wrote: Hello Adrian, Thank you for your response. Sorry about the typos in the previous post. I will try to explain myself more clearly. This is my first function to create a dynamic query and it is as follows: This works fine. It accepts 2 sql

[GENERAL] postgres user with password read-only user without?

Is there a way to configure authentication so that some users require a password and other users don't? Ted -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general