Re: [GENERAL] Support for \u0000?

I see. Thanks for the quick responses! On Wed, Jul 19, 2017 at 11:32 PM, Tom Lane wrote: > Matthew Byrne writes: > > Would a more feasible approach be to introduce new types (say, TEXT2 and > > JSONB2 - or something better-sounding) which are the same

Re: [GENERAL] Support for \u0000?

Thanks for the response Tom. I understand this would be a mammoth task. Would a more feasible approach be to introduce new types (say, TEXT2 and JSONB2 - or something better-sounding) which are the same as the old ones but add for support \u and UTF 0? This would isolate nul-containing byte

Re: [GENERAL] Support for \u0000?

Matthew Byrne writes: > Would a more feasible approach be to introduce new types (say, TEXT2 and > JSONB2 - or something better-sounding) which are the same as the old ones > but add for support \u and UTF 0? This would isolate nul-containing > byte arrays to the

Re: [GENERAL] Support for \u0000?

Matthew Byrne writes: > Are there any plans to support \u in JSONB and, relatedly, UTF code > point 0 in TEXT? No. It's basically never going to happen because of the widespread use of C strings (nul-terminated strings) inside the backend. Making \0 a legal member of

[GENERAL] Support for \u0000?

Are there any plans to support \u in JSONB and, relatedly, UTF code point 0 in TEXT? To the best of my knowledge \u is valid in JSON and code point 0 is valid in UTF-8 but Postgres rejects both, which severely limits its usefulness in many cases. I am currently working around the issue

Re: [GENERAL] Support for BDR in 9.5?

On January 8, 2016 7:42:06 PM GMT+01:00, "Andrew Biggs (adb)" wrote: >On 1/8/16, 10:53 AM, Rob Sargent wrote: > >On 01/08/2016 10:39 AM, Andrew Biggs (adb) wrote: >Can anyone tell me if PostgreSQL 9.5 supports (either natively or by >extension) the BDR functionality? > >I tried

Re: [GENERAL] Support for BDR in 9.5?

On 1/8/16, 10:53 AM, Rob Sargent wrote: On 01/08/2016 10:39 AM, Andrew Biggs (adb) wrote: Can anyone tell me if PostgreSQL 9.5 supports (either natively or by extension) the BDR functionality? I tried it out and ran into issues, but it could well have been I was doing something wrong. Thanks!

Re: [GENERAL] Support for BDR in 9.5?

On 01/08/2016 10:42 AM, Andrew Biggs (adb) wrote: Installed 9.5 to CentOS7 via yum, and tried going through the BDR quick-start guide (minus sections 2.1): http://bdr-project.org/docs/stable/quickstart.html It was unhappy that BDR binaries were not on the path, and failed at section 2.4.

Re: [GENERAL] Support for BDR in 9.5?

On 01/08/2016 10:39 AM, Andrew Biggs (adb) wrote: Can anyone tell me if PostgreSQL 9.5 supports (either natively or by extension) the BDR functionality? I tried it out and ran into issues, but it could well have been I was doing something wrong. Thanks! Andrew I'm sure those who might

Re: [GENERAL] Support for BDR in 9.5?

Afaik no, you have to use 9.4. Am 8. Januar 2016 18:39:07 MEZ, schrieb "Andrew Biggs (adb)" : >Can anyone tell me if PostgreSQL 9.5 supports (either natively or by >extension) the BDR functionality? > >I tried it out and ran into issues, but it could well have been I was >doing

Re: [GENERAL] Support for BDR in 9.5?

On 8 January 2016 at 18:56, Joshua D. Drake wrote: > On 01/08/2016 10:42 AM, Andrew Biggs (adb) wrote: > > Installed 9.5 to CentOS7 via yum, and tried going through the BDR >> quick-start guide (minus sections 2.1): >> >> http://bdr-project.org/docs/stable/quickstart.html

Re: [GENERAL] Support for BDR in 9.5?

On 1/8/16, 12:51 PM, "Simon Riggs" > wrote: On 8 January 2016 at 18:56, Joshua D. Drake > wrote: On 01/08/2016 10:42 AM, Andrew Biggs (adb) wrote: Installed 9.5 to CentOS7 via yum, and

[GENERAL] Support for BDR in 9.5?

Can anyone tell me if PostgreSQL 9.5 supports (either natively or by extension) the BDR functionality? I tried it out and ran into issues, but it could well have been I was doing something wrong. Thanks! Andrew

Re: [GENERAL] Support for hardware tokens for server/replication private key

Thanks for the reply. I can now confirm that replication connections can work using a private key stored on a hardware token. Do you know if there's any way I can store the server key on the hardware token? -- View this message in context:

Re: [GENERAL] Support for hardware tokens for server/replication private key

On Thu, Dec 3, 2015 at 5:31 AM, mdaswani wrote: > Hi, > > Postgres allows client-side SSL requests to use secret keys on hardware > tokens via OpenSSL engine support. Is there an equivalent way to store the > server key on a hardware token. > > Similarly, is it

[GENERAL] Support for hardware tokens for server/replication private key

Hi, Postgres allows client-side SSL requests to use secret keys on hardware tokens via OpenSSL engine support. Is there an equivalent way to store the server key on a hardware token. Similarly, is it possible to specify private keys on a hardware token for replication connections? Does the

[GENERAL] support for ltree

I am wondering if the contributed module ltree will always be part of Postgres? Do contributed modules ever get absorbed into Postgres itself? The reason I am asking is that, although ltree seems to have been a contributed module since at least 8.3, how can one know if it will always be part of

Re: [GENERAL] support for ltree

Geometric Data Types have been in PostgreSQL for quite a while. http://www.postgresql.org/docs/9.2/interactive/datatype-geometric.html JSON have been in PostgreSQL since 9.2 and it's functionality increases with each new version. http://www.postgresql.org/docs/9.2/interactive/datatype-json.html

Re: [GENERAL] support for ltree

Hi Melvin, Thanks for this response. It still leave my question unanswered. I should rephrase it -- will ltree become a native datatype in Postgres (as opposed to remaining an extension). Are there any plans to make ltree a native datatype? Michael On Fri, Jun 12, 2015 at 7:58 AM, Melvin

Re: [GENERAL] support for ltree

On Friday, June 12, 2015, Michael Shapiro mshapir...@gmail.com wrote: Hi Melvin, Thanks for this response. It still leave my question unanswered. I should rephrase it -- will ltree become a native datatype in Postgres (as opposed to remaining an extension). Are there any plans to make ltree

Re: [GENERAL] support for ltree

Michael Shapiro mshapir...@gmail.com writes: Thanks for this response. It still leave my question unanswered. I should rephrase it -- will ltree become a native datatype in Postgres (as opposed to remaining an extension). Are there any plans to make ltree a native datatype? No. That is not

Re: [GENERAL] support for ltree

On Friday, June 12, 2015, Michael Shapiro mshapir...@gmail.com wrote: The reason I am asking is that, although ltree seems to have been a contributed module since at least 8.3, how can one know if it will always be part of subsequent versions of Postgres? Whether contrib, core, or an

Re: [GENERAL] Support functions for GiST index on citext

On Sat, Aug 16, 2014 at 7:02 PM, Chris Hanks christopher.m.ha...@gmail.com wrote: Thanks, I have considered it, and I'd like to stick with an array for my use case if possible. Also, if citext is being advised against, I'd like to know about it, since I use it extensively and have never had an

Re: [GENERAL] Support functions for GiST index on citext

Have you considered normalizing? Here's a SQLFiddle example: http://sqlfiddle.com/#!15/61897/3/0. It uses text instead of citext, but I imagine your results should be similar. Also, I think usage of citext is generally recommended against. The basic idea is to not use an array but use a second

Re: [GENERAL] Support functions for GiST index on citext

Thanks, I have considered it, and I'd like to stick with an array for my use case if possible. Also, if citext is being advised against, I'd like to know about it, since I use it extensively and have never had an issue with it. Can anyone shed some light on this? Thanks! Chris On Sat, Aug 16,

[GENERAL] Support functions for GiST index on citext

Hi - I have a table with a citext[] column, and I'm trying to write a uniqueness constraint for the array values. That is, two rows with {one,two} and {two,three} would conflict. Since it's citext, also {one,two} and {TWO, THREE} should conflict too. My first thought was to make a unique index

[GENERAL] Support for Alert

Hi, PostgreSQL have a way to put alerts about number of connections, tablespace used, etc like the DBMS_SERVER_ALERT package of Oracle? Thanks you

Re: [GENERAL] Support for Alert

On 02/19/2014 08:49 AM, Alejandro Carrillo wrote: Hi, PostgreSQL have a way to put alerts about number of connections, tablespace used, etc like the DBMS_SERVER_ALERT package of Oracle? Thanks you No but any number of monitoring systems already support PostgreSQL: Zabbix, New Relic,

Re: [GENERAL] Support for Alert

Have a look here http://bucardo.org/wiki/Check_postgres Regards On Wednesday, February 19, 2014 5:51 PM, Alejandro Carrillo faster...@yahoo.es wrote: Hi, PostgreSQL have a way to put alerts about number of connections, tablespace used, etc like the DBMS_SERVER_ALERT package of Oracle?

Re: [GENERAL] Support for Foreign keys with arrays

Thanks, not sure how to download and apply this patch, not getting any down load link. ? On Wed, Jul 10, 2013 at 9:16 AM, Michael Paquier michael.paqu...@gmail.comwrote: On Tue, Jul 9, 2013 at 6:26 PM, itishree sukla itishree.su...@gmail.com wrote: Hello Every one, I have a requirement

Re: [GENERAL] Support for Foreign keys with arrays

On Wed, Jul 10, 2013 at 3:10 PM, itishree sukla itishree.su...@gmail.com wrote: Thanks, not sure how to download and apply this patch, not getting any down load link. ? In the section Comments, some of the lines are referred by patch. Click on the latest one. You will be redirected to the email

[GENERAL] Support for Foreign keys with arrays

Hello Every one, I have a requirement for support for foreign keys with arrays, which is not there in postgresql 9.2, however it is in development for 9.3, i can see there is some thread saying patch is available, can any one please help me to get the patch, or any other work around by which we

Re: [GENERAL] Support for Foreign keys with arrays

On Tue, Jul 9, 2013 at 6:26 PM, itishree sukla itishree.su...@gmail.com wrote: Hello Every one, I have a requirement for support for foreign keys with arrays, which is not there in postgresql 9.2, however it is in development for 9.3, i can see there is some thread saying patch is available,

[GENERAL] Support of multibyte encoding for pg_trgm

Teodor, I ran across a commit message that shows multibyte encoding support in 8.4 and my testing shows that to be the case as well. Is there a back patch for 8.2? My own quick attempt at creating one didn't work so well and before I start spending some major time trying I thought

Re: [GENERAL] support for embedded db and a clustered index?

Scott Marlowe wrote: Also, can pgsql be embedded in an application? By that I mean it is easily deployable with an application. Not really the same thing. PostgreSQL is not embeddable in the classic sense, and if you need an embedded database, look at SQLLite. ... I do NOT mean

Re: [GENERAL] support for embedded db and a clustered index?

Hi all, Does pgsql provide support for a clustered index? By that I mean can I specify that the database insert records in the order of a particular attribute. Many of my queries are time-range based and my row inserts are done chronologically, so it would benefit to have them sorted by when

Re: [GENERAL] support for embedded db and a clustered index?

On Sat, Oct 25, 2008 at 12:02 PM, Julian Bui [EMAIL PROTECTED] wrote: Hi all, Does pgsql provide support for a clustered index? By that I mean can I specify that the database insert records in the order of a particular attribute. Many of my queries are time-range based and my row inserts

[GENERAL] Support for distributed transactions in 8.2.5

Hi, I've read through the relevant documentation on distributed transactions for PostgreSQL 8.2.5 but it leaves me with more questions than answers. It is unclear to me how SQL statements can be executed at remote nodes from a single coordinator and then use distributed two-phase commit (via

Re: [GENERAL] Support for distributed transactions in 8.2.5

Brian Oki (boki) wrote: My question is this: How does PostgreSQL 8.2.5 execute DML statements (insert, update, delete, select) on remote nodes as part of the same transaction? Where is the syntax specified? Or, is there a different model supported? It's sort of like the synchronous multi-master

Re: [GENERAL] Support for distributed transactions in 8.2.5

On Thursday 11 October 2007 11:50, Richard Huxton wrote: Brian Oki (boki) wrote: My question is this: How does PostgreSQL 8.2.5 execute DML statements (insert, update, delete, select) on remote nodes as part of the same transaction? Where is the syntax specified? Or, is there a different

Re: [GENERAL] Support for idempotent schema changes?

Joshua D. Drake wrote: David Lowe wrote: Within the context of a script, executing: Begin Statement1 Statement2 Statement3 Commit Where I only wish to commit if the error is specific to the object already existing, and rollback for all other errors, what's the best way to accomplish that?

Re: [GENERAL] Support for idempotent schema changes?

Peter Eisentraut wrote: You just ignore the error if the object already exists. I'd advice against that or at least make sure that only the thing already exists errors get ignored. Because otherwise it's 100% impossible to discover any real problems with the scripts. -- Regards Flemming

Re: [GENERAL] Support for idempotent schema changes?

Eisentraut [mailto:[EMAIL PROTECTED] Sent: Saturday, March 03, 2007 11:45 PM To: pgsql-general@postgresql.org Cc: David Lowe Subject: Re: [GENERAL] Support for idempotent schema changes? David Lowe wrote: So how can I make statements of the form: * alter table only customers add constraint

Re: [GENERAL] Support for idempotent schema changes?

Cc: David Lowe Subject: Re: [GENERAL] Support for idempotent schema changes? David Lowe wrote: So how can I make statements of the form: * alter table only customers add constraint a_previously_missed_constraint unique (a, b, c); * add column points int4 not null default 0

[GENERAL] Support for idempotent schema changes?

At our development shop we use many different PostgreSQL databases simultaneously, each corresponding to a specific version of our software. For example, a developer might be working on v1.0 and v1.1 at the same time, while QA is busily testing/verifying version 1.0.3. All application code and

Re: [GENERAL] Support for idempotent schema changes?

David Lowe wrote: So how can I make statements of the form: * alter table only customers add constraint a_previously_missed_constraint unique (a, b, c); * add column points int4 not null default 0; idempotent? You just ignore the error if the object already exists. -- Peter

Re: [GENERAL] Support for Limit in Update, Insert...

Well, I do have a use case for it. Context: We have data coming in from web requests, which must be fast, so we just insert them in temporary tables without any verification. Then they are periodically processed by a background task, but even that one will process just a chunk at a time to

Re: [GENERAL] Support for Limit in Update, Insert...

On Thu, Sep 08, 2005 at 10:49:25PM -0400, Tom Lane wrote: Alvaro Herrera [EMAIL PROTECTED] writes: This has been discussed before, and rejected. Please see the archives. For SELECT, both LIMIT and OFFSET are only well-defined in the presence of an ORDER BY clause. (One could argue that we

Re: [GENERAL] Support for Limit in Update, Insert...

On Fri, Sep 09, 2005 at 06:42:10PM -0500, Jim C. Nasby wrote: On Thu, Sep 08, 2005 at 10:49:25PM -0400, Tom Lane wrote: Alvaro Herrera [EMAIL PROTECTED] writes: This has been discussed before, and rejected. Please see the archives. For SELECT, both LIMIT and OFFSET are only

[GENERAL] Support for Limit in Update, Insert...

Would be any future support for limit in update/insert queries? so you could do something like update table1 set col1=value1 limit 1000; would update just the first 1000 rows in the table. I've been playing a little with the SPI and I get the SPI already has the support for limit the

Re: [GENERAL] Support for Limit in Update, Insert...

Cristian Prieto [EMAIL PROTECTED] writes: Would be any future support for limit in update/insert queries? so you = could do something like update table1 set col1=3Dvalue1 limit 1000; would update just the first 1000 rows in the table. That seems like a spectacularly bad idea, considering that

Re: [GENERAL] Support for Limit in Update, Insert...

Maybe the first 1000 rows based in the primary index - Original Message - From: Tom Lane [EMAIL PROTECTED] To: Cristian Prieto [EMAIL PROTECTED] Cc: pgsql-general@postgresql.org Sent: Thursday, September 08, 2005 6:05 PM Subject: Re: [GENERAL] Support for Limit in Update, Insert

Re: [GENERAL] Support for Limit in Update, Insert...

On Thu, Sep 08, 2005 at 07:19:34PM -0600, Cristian Prieto wrote: Maybe the first 1000 rows based in the primary index No, this is not a satisfactory answer, because 1. it's possible that there's no primary key at all, or 2. said index may not get used for the execution of the update. Maybe

Re: [GENERAL] Support for Limit in Update, Insert...

Alvaro Herrera [EMAIL PROTECTED] writes: This has been discussed before, and rejected. Please see the archives. For SELECT, both LIMIT and OFFSET are only well-defined in the presence of an ORDER BY clause. (One could argue that we should reject them when no ORDER BY, but given that the

[GENERAL] support

hi,pgsql-genera I am chinese user, I have installed thd PostGreSQL 8.0 for win in my computer, it's very good. but I find a problem, when I use select * from dcvalue where text_value='' to search record, the system return no results, moreover when I use select * from dcvalue where

Re: [GENERAL] support

wrote: hi,pgsql-genera I am chinese user, I have installed thd PostGreSQL 8.0 for win in my computer, it's very good. but I find a problem, when I use select * from dcvalue where text_value='' to search record, the system return no results, seems like your locale setting doesn't match

[GENERAL] support on postgres

Hello, We develop SMS application using a proprietary framework installed on Linux server. This framework installs and creates Postgres 7.1 data base under /var/lib partition. Client notices that /var/lib partition seems too small for SMS application activity. Client would like to move postgres

Re: [GENERAL] Support.

Louis P. Boudville wrote: 1.Where can I get end user support for PostgreSQL ? You could use this mailing list, the #postgresql channel on the Freenode IRC server or do a search for commercial Postgres support. The techdocs on the Postgresql.org site would be my first stop, and you can also

[GENERAL] Support for functions returning mutliple result sets?

I know I can write plpgsql functions that return sets. Does postgres support returning multiple sets from a function? Bill McMilleon ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate

Re: [GENERAL] Support for functions returning mutliple result sets?

[EMAIL PROTECTED] wrote: I know I can write plpgsql functions that return sets. Does postgres support returning multiple sets from a function? No. Joe ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate

Re: [GENERAL] Support for functions returning mutliple result sets?

[EMAIL PROTECTED] writes: Does postgres support returning multiple sets from a function? Not directly. You can fake it in some cases by returning several open cursors and expecting the caller to fetch from those cursors. However, if you can't write SQL queries that can be executed to return

[GENERAL] support

I am looking at PostgreSQL as a possible option for our backend database. I am also evaluating Oracle. What kind of paid support does PostgreSQL offer? Jason Tesser Web/Multimedia Programmer Northland Ministries Inc. (715)324-6900 x3050 ---(end of

Re: [GENERAL] Support of type procedure

Mourad EL HADJ MIMOUNE writes: I have read in some document about Postgres that this last supports attrubutes of type procedure. Type procedure allows values of an attribute to be represented by a procedure. This presumably existed in or near Berkeley POSTGRES 4.2, and some support code is

[GENERAL] Support for Geometric Types

I have a couple questions regarding the maturity of the support for geometric types: - is there support for indexing geometric types so that things like '=' operators and some of the other geometric operators are a bit faster? - are there any plans on extending some of the geometric operators