On Fri, Mar 06, 2015 at 03:24:28PM +0530, Medhavi Mahansaria wrote:
> aml_db=> \d+ check_date
> Table "public.check_date"
> Column |Type | Modifiers | Storage | Stats
> target | Description
> ---+-+--
On Fri, Mar 06, 2015 at 02:39:34AM -0700, wambacher wrote:
> some comments:
>
> - the OOM did not kill the Postmaster but the Analyze-Job.
> - started with 24GB real and 18GB Swap - that must be enought! --> killed
"Back in the days" it was conventional wisdom to have twice
as much swap as you'v
On Sat, Apr 18, 2015 at 08:09:43AM +1000, rob stone wrote:
> I'm trying to upgrade from 9.3 to 9.4 on my laptop and encountering this
> error:-
>
>
> postgres@roblaptop:/usr/lib/postgresql/9.4/bin$ ./pg_upgrade
> -b /usr/lib/postgresql/9.3/bin -B /usr/lib/postgresql/9.4/bin
> -d /home/postgres/d
> Anyway, I agree that you have to store the time zone *somewhere*, and I
> suppose that's the reason Joshua remarked that you really shouldn't use
> WITHOUT TIME ZONE. And often a time has one perspective that is
> "canonical" or "preferred", e.g. the time zone of the user who created
> the ob
> It's probably worth noting that both the Ruby 'best practice' AND
> Postgres have a failure case when dealing with future dates precisely
> because they are storing the data as UTC with a time zone. This is
> one case where storing the data WITHOUT TIME ZONE would actually save
> your bacon.
>
On Fri, May 22, 2015 at 09:46:10AM +0100, Tim Clarke wrote:
> On 22/05/15 09:40, Alban Hertroys wrote:
> > On 21 May 2015 at 23:42, Karsten Hilbert wrote:
> >
> >> You are right in the following aspect:
> >>
> >> - client sends in "NOW at HERE&quo
ake schema changes on
> the fly", then I'd simply say "no sale". Of course, in regards to the
> schema, it would be proper to document what the DBA needs to do to set up
> the data base with the proper tables and other items.
In fact, an app might have an opt
On Thu, Jul 23, 2015 at 12:28:32PM -0600, Rob Sargent wrote:
> I'm suggesting OP might find changing truncate statements to deletes
> (without a where clause) a simpler solution. Something has to change.
Well, OP isn't looking for a solution to "delete all rows"
but rather to _prevent_ deletion.
On Wed, Jul 29, 2015 at 10:03:56PM +0530, Ramesh T wrote:
> Hi All,
>is instr available in postgres 9.3..?
>
> in oracle instr('12.32.42','.',-1) ,
>
> any ...
http://www.postgresql.org/docs/9.3/static/index.html
> ... help appreciated
You are welcome !
Karsten
--
GPG key
On Sat, Aug 22, 2015 at 11:15:07AM -0400, Melvin Davidson wrote:
> PostgreSQL Developer Best Practices
>
> 1. Prefix ALL literals with an Escape
>EG: SELECT E'This is a \'quoted literal \'';
> SELECT E'This is an unquoted literal';
>
>Doing so will prevent the annoying "WARNING:
On Tue, Aug 25, 2015 at 02:02:17PM +1200, Gavin Flower wrote:
> On 25/08/15 01:15, Ray Cote wrote:
> >On Sat, Aug 22, 2015 at 11:46 AM, Karsten Hilbert ><mailto:karsten.hilb...@gmx.net>> wrote:
> >
> [...]
> >
> >9. Do NOT arbitrarily assign an &quo
> No one ever said a number is not natural. just that there is no need to
> duplicate uniqueness
> with a separate number.
The whole point is that people are telling you that surrogate keys do not
_duplicate_ uniqueness but
rather _generate_ it, artificially, and therefore reliably.
Today's ext
> In most cases developers don’t care about index, unique, foreign key, or
> primary key names (from a coding standpoint)
Until the day they'd like to write a reliable database change script.
(PG's internal conventions for object names _have_ changed over the years)
Karsten
--
Sent via pgsql
On Wed, Aug 26, 2015 at 09:04:08AM -0400, John Turner wrote:
> >>>In most cases developers don’t care about index, unique, foreign key,
> >>>or primary key names (from a coding standpoint)
> >>
> >>Until the day they’d like to write a reliable database change script.
> >
> >Not sure I understand.
I have searched the mailing list archives as well as the
internet at large but haven't been able to find a _streaming_
version of md5 hashing for large objects. The closest thing I
found is this thread
http://www.postgresql.org/message-id/5d0f60990704081003p615530acx86257a70bff33...@mail.
t; objects in a database.
ACID. Permissions. Single access method.
> Also, the max size of a value is 1GB.
The maximum size is 4 Terabyte ATM for large objects.
Karsten Hilbert
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Fri, Oct 02, 2015 at 10:06:55AM -0400, Tom Lane wrote:
> The problem you'll have in defining timetzrange is that you first need to
> invent a "timetz - timetz" operator, which doesn't exist as a builtin
> function because the behavior seems not well-defined. What would you do
> with the timezo
On Mon, Oct 05, 2015 at 03:27:26PM +, Kevin Grittner wrote:
> Karsten Hilbert wrote:
>
> > I am dealing with radiology studies aka DICOM data) one would
> > want an md5 function which streams in parts of a large object
> > piece by piece using md5_update and m5_fin
On Mon, Oct 05, 2015 at 03:27:26PM +, Kevin Grittner wrote:
> Karsten Hilbert wrote:
>
> > I am dealing with radiology studies aka DICOM data) one would
> > want an md5 function which streams in parts of a large object
> > piece by piece using md5_update and m5_fin
On Wed, Oct 07, 2015 at 12:55:38PM +0200, Karsten Hilbert wrote:
> > > I am dealing with radiology studies aka DICOM data) one would
> > > want an md5 function which streams in parts of a large object
> > > piece by piece using md5_update and m5_finalize or some such
On Wed, Oct 07, 2015 at 01:30:24PM +0200, Pavel Stehule wrote:
> > > > > I am dealing with radiology studies aka DICOM data) one would
> > > > > want an md5 function which streams in parts of a large object
> > > > > piece by piece using md5_update and m5_finalize or some such.
> > > > It would ce
For the record - I have also devised another solution to the
underlying problem (md5(bytea) cannot process large amounts
of input), chunked md5():
create or replace function lo_chunked_md5(oid, int)
returns text
language 'plpgsql'
stable stri
On Wed, Oct 07, 2015 at 01:01:41PM -0500, Jim Nasby wrote:
> >Still, I'd welcome a native, streaming md5(loid) which is
> >bound to be more optimized by design.
>
> It would be nice if we had an interface to TOAST that allowed for streaming
> (well, really chunking) data to a function. That would
On Mon, Oct 12, 2015 at 12:14:10PM -0500, Jim Nasby wrote:
> On 10/4/15 6:18 AM, Karsten Hilbert wrote:
> > check whether both TZs are equal,
> > if so
> > ignore them
> > else
> > convert both operands to UTC,
> > do
On Tue, Oct 13, 2015 at 03:44:15PM -0700, John R Pierce wrote:
> On 10/13/2015 3:27 PM, droberts wrote:
> >Thanks. My only question is how do you create a schema diagram (ERD) then?
> >The tool won't know what the relationships are unless maybe you put foreign
> >key constraints on. BTW does an
On Fri, Oct 16, 2015 at 02:28:25PM +1300, Gavin Flower wrote:
> Since 'id' is only used to indicate a PRIMARY KEY, there is less confusion
> in joins, and it is clear when something is a foreign key rather than a
> PRIMARY KEY.
Given that "id" often has meaning outside the database I much
prefer
On Fri, Oct 16, 2015 at 04:59:12PM -0500, Jim Nasby wrote:
> BTW, I found Karsten's idea of using 'pk' for the surrogate key, and
> fk_table_name interesting. It helps avoid ambiguity from externally
> generated ID values.
That's the point :-)
Here's a real live schema using (mostly) the above a
> > Here's a real live schema using (mostly) the above approach:
> >
> > http://www.gnumed.de/~ncq/gnumed/schema/gnumed_v20/
> >
> > in case anyone is interested in taking a look.
> >
> > Karsten
>
> Apparently (according to your naming convention) several tables (such as
> 'clin.substance_in
On Mon, Oct 19, 2015 at 04:25:39AM -0500, Jim Nasby wrote:
> BTW, if there's any interest, I have code that sets up a non-inheritance
> table specifically for doing foreign keys to the inheritance parent. It
> doesn't support updates right now, but should be fully safe from a FK
> standpoint.
Can
On Sun, Oct 25, 2015 at 08:32:43AM -0700, David Blomstrom wrote:
> Someone said when you add a new column in Postgre, it's appended to the end
> of the table. Does that mean that's where it has to stay, or can you
> rearrange columns
No, unless you drop/re-create the table (manually or with
On Thu, Jun 30, 2016 at 09:16:49AM -0500, Merlin Moncure wrote:
> It's not really necessary to create version down scripts. In five
> years of managing complex database environments we've never had to
> roll a version back and likely never will; in the event of a disaster
> it's probably better t
On Tue, Jul 12, 2016 at 12:25:08PM +0100, Miguel Ramos wrote:
> > # pg_restore -d recovery /mnt/paysdeloire2013_convertida2.1.dump
> > pg_restore: [custom archiver] out of memory
> > 12:09:56.58 9446.593u+1218.508s 24.3% 167+2589k 6+0io 0pf+0sw 6968822cs
...
> I suspect that the restore fails
On Mon, Aug 01, 2016 at 12:48:57PM -0400, Rakesh Kumar wrote:
> Can an existing stored procedure be modified online while other users
> are executing it. In Oracle, the session doing CREATE OR REPLACE
> PACKAGE would wait for other session to complete. Once the package is
> changed, first time oth
On Thu, Aug 11, 2016 at 11:04:37AM -0600, support-tiger wrote:
> #1) pg_hba conf
> Out of the box the md5 setting blocks access. Most "advice" say change to
> "all all trust" and indeed that works. But that seems a big security issue.
> Specifying a postgres role, password, and peer does not seem
På fredag 12. august 2016 kl. 10:33:19, skrev Chris Travers
:
> My preference is stored procedures plus service locators
I know your work on the former with respect to the financial app you are
working on.
Would you care to elaborate a little on the latter (service locators) ?
Thanks,
Karsten
On Fri, Aug 12, 2016 at 01:32:33PM +0200, Chris Travers wrote:
>>> My preference is stored procedures plus service locators
>>
>> Would you care to elaborate a little on the latter (service locators) ?
>>
>
> Sure. What I prefer to do is to allow for a (cacheable) lookup on the
> basis of some c
Hello Chris,
I am getting closer but ...
> > > Sure. What I prefer to do is to allow for a (cacheable) lookup on the
> > > basis of some criteria, either:
> > > 1. Function name or
> > > 2. Function name and first argument type
> > >
> > > This assumes that whichever discovery criteria you are
On Sun, Aug 14, 2016 at 04:02:19PM +0200, Chris Travers wrote:
> One example is of such a service locator is
> http://search.cpan.org/dist/PGObject-Simple/lib/PGObject/Simple.pm
>
> It runs as a library which helps the program decide how to do the call.
> Currently it looks in the system catalog
On Mon, Sep 19, 2016 at 02:10:50PM +0200, Kiran wrote:
> EXPLAIN ANALYZE select * from question where weighted_tsv @@
> to_tsquery('Hur&ofta');
>
> I get the following output
>
> "Bitmap Heap Scan on question (cost=12.33..25.38 rows=10 width=731)
> (actual time=0.058..0.062 rows=3 loops=1)"
> "
On Mon, Sep 19, 2016 at 02:56:17PM +0200, Kiran wrote:
> I want to know whatever the Analyze output I am getting is normal for a
> table having few records or something is wrong.
> Will the DB engine uses whatever the best way to execute a query
> irrespective of the indexing in this case?
It wil
On Sat, Oct 01, 2016 at 07:21:47PM -0400, Melvin Davidson wrote:
> *I would like to comment on the multiple schema vs databases situation.
> First of all, 1000's of databases is insanity and just asking for trouble.
> Next, 1000's of schemas is a nightmare to maintain. I understand the
> requireme
On Wed, Oct 19, 2016 at 01:24:10PM +1300, Patrick B wrote:
> I'm using pg_sample to do that, but unfortunately it doesn't work well.
> It doesn't get the first 100 rows. It gets random 100 rows.
>
> Do you guys have any idea how could I do this?
For any relevant answer to this question you'll ha
On Mon, Oct 31, 2016 at 09:14:07AM -0400, Melvin Davidson wrote:
>> Maybe create an event trigger that updates a simple table with the last
>> modification time or sends a notification?
...
> That would certainly work, but
> the problem is, that trigger would have to be created for every table in
On Tue, Nov 15, 2016 at 10:49:42AM +0530, kaustubh kelkar wrote:
> The issue is not with server , it is running fine .
> Issue is not with port either , for local machine,
The issue is with:
> I guess [...]
Regards,
Karsten
> firewall won't affect.
>
>
> On Tue, Nov 8, 2016 at 8:14 PM, Adr
>>> The issue is not with server , it is running fine .
>>>Issue is not with port either , for local machine,
>> The issue is with:
>>I guess [...]
>I have no idea what you're saying ...
I figured the firewall might be an issue. Or it might not.
But guessing won't tell.
Regards,
Karsten
--
S
On Thu, Dec 01, 2016 at 12:38:37AM +1300, Samuel Williams wrote:
> Is there any reason why for the same data set, and same indexes, that
> the data in postgres would be significantly larger than
> innodb/mariadb?
Sure: because they do entirely different things on-disk.
Regards,
Karsten
--
GPG k
On Wed, Nov 30, 2016 at 12:00:07PM +, Howard News wrote:
> recently I had problems with a corrupt pg_dump file. The problem with the
> file was due to a faulty disk. The trouble with this is that I was unaware
> of the disk problem and the pg_dump file corruption so I did not have a full
> val
On Wed, Nov 30, 2016 at 01:11:58PM +, Howard News wrote:
> > You can try to suitably combine "pg_dump --format=plain" with
> > "tee" and "md5sum" such that the output stream is diverted to
> > both a file and a pipe-into-CRC-algorithm and eventually
> > compare the pipe's sum with the sum gene
On Wed, Nov 30, 2016 at 01:53:21PM +, Howard News wrote:
> Regarding the filesystem solution, the dump is currently written to a HP
> > > RAID 10 array with an NTFS partition. What filesystems / raid arrays have
> > > this ability?
> > If you can't trust your RAID 10 (1 meaning mirrored) to
>
Also this
https://en.wikipedia.org/wiki/Silent_data_corruption#Countermeasures
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscript
On Wed, Dec 07, 2016 at 07:57:54AM -0800, Rich Shepard wrote:
> I have used '-- ' to enter comments about tables or columns and am curious
> about the value of storing comments in tables using the COMMENT key word.
> When is the latter more appropriate than the former?
"--" only means "comment"
On Thu, Dec 08, 2016 at 07:47:56PM -0500, Metare Solve wrote:
> But, what I'm gathering is, you think this is a crutch too. Will Python
> enable me to do the same things that I do with that kind of big data
> processing program?
Yes and no. Python will enable you to do _way_ more (because
you tel
> Many applications are not designed to have a "stable" database API.
It seems OP is arguing they should.
Regards,
Karsten
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Fri, Dec 30, 2016 at 10:23:44AM -0500, Stephen Frost wrote:
> One area that isn't fully addressed with the PG auth model today is
> partial access to a certain column. Consider a table where you want
> users to have access to all of the rows and all of the columns *except*
> for column X for r
On Wed, Jan 11, 2017 at 05:54:11PM -0700, David G. Johnston wrote:
> I don't see where "call a setup function immediately after connecting"
Sounds like a "login trigger", more generally an ON CONNECT
event trigger, which we don't have at the moment as far as I
know.
One of the main arguments aga
On Tue, Jan 17, 2017 at 09:25:38AM +0100, Thomas Kellerer wrote:
> I recently stumbled over the need to use a wildcard escape character for a
> condition that makes use of LIKE ANY, something like:
>
>select *
>from some_table
>where name like any (array['foo_bar%', 'bar_foo%']) esca
On Tue, Jan 17, 2017 at 03:27:57PM +0100, Thomas Kellerer wrote:
>> Do you need to have the _ NOT be recognized as a wildcard ?
>
> Yes, the underscore should NOT be a wildcard in this case.
Understood.
So, as Tom hinted at, your best bet might be to write a
function escape_underscore_
gt; 3. How can we transparent data encryption in Postgres?
The information you need to answer your questions is found here:
https://www.postgresql.org/docs/devel/static/index.html
Regards,
Karsten Hilbert
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4
On Tue, Nov 17, 2015 at 05:48:36PM +0530, Ramesh T wrote:
> the query is big it's selecting 20 rows from two table like i mentioned
> above exaplain analyze
>
> what should i do..?any help
Considering to post the query might be a reasonable first step.
Karsten
> On Wed, Nov 4, 2015 at 4:27 AM,
On Thu, Nov 19, 2015 at 09:01:47AM -0600, Merlin Moncure wrote:
> It's quite a stretch to assume that HIPAA applies to internal garbage
> collection minutia.
It, of course, does.
Which is why applying your suggestion ...
> A much better way to look at compliance is to encrypt all sensitive
> de
On Thu, Nov 26, 2015 at 03:35:49PM +0100, kri...@tvnetwork.hu wrote:
> We have run into a case where we run a long transaction, and during the
> transaction the backend process's memory usage is growing constantly.
>
> I've written a script to simulate this, please someone confirm if it is
> norm
On Thu, Nov 26, 2015 at 04:58:25PM +0100, Kojedzinszky Rich�rd wrote:
> Do you mean the scripting language? Originally we use C++ code with tntdb
> (from http://www.tntnet.org/) with the same symptons/issues.
That (perl and c++ showing the same) should indeed rule out a language issue.
Karsten
-
On Mon, Dec 14, 2015 at 09:55:02AM -0800, Benjamin Smith wrote:
> Is that there is a way to let the query succeed, but nullify any fields where
> read permissions fail?
What about real field values begin NULL ?
Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73B
te successfully used a
semi-structured mentoring effort to attract new package maintainers:
https://wiki.debian.org/DebianMed/MoM
For what it is worth...
Karsten Hilbert
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.po
On Wed, Jan 06, 2016 at 11:22:17AM -, FarjadFarid(ChkNet) wrote:
> I am not in favour of massive price structures but that
> there should be $100-$200 costs for smallest version. Times
> several million products. This may allow postgresql to reduce
> its prices on its the top of the range prod
Hi,
I have attempted a pg_upgrade on Debian using the Debian
wrapper scripts like so:
pg_upgradecluster -v 9.5 9.4 main
(meaning to upgrade a cluster named "main" from 9.4 to 9.5)
which resulted in this:
-
On Fri, Jan 08, 2016 at 12:45:29PM +0100, Karsten Hilbert wrote:
> pg_restore: erstelle EXTENSION „pg_trgm“
> pg_restore: erstelle COMMENT „EXTENSION "pg_trgm"“
> pg_restore: erstelle FUNCTION „pg_catalog.gtrgm_in("cstring")“
> pg_resto
On Fri, Jan 08, 2016 at 12:45:29PM +0100, Karsten Hilbert wrote:
> pg_restore: erstelle EXTENSION „pg_trgm“
> pg_restore: erstelle COMMENT „EXTENSION "pg_trgm"“
> pg_restore: erstelle FUNCTION „pg_catalog.gtrgm_in("cstring")“
> pg_resto
On Fri, Jan 08, 2016 at 07:18:24AM -0800, Adrian Klaver wrote:
> http://www.postgresql.org/docs/9.5/interactive/pgupgrade.html
>
> "If an error occurs while restoring the database schema, pg_upgrade will
> exit and you will have to revert to the old cluster as outlined in step 16
> below.
Thanks
On Fri, Jan 08, 2016 at 07:41:09AM -0800, Adrian Klaver wrote:
> >On Fri, Jan 08, 2016 at 07:18:24AM -0800, Adrian Klaver wrote:
> >
> >>I thought --method=dump was the default, so this:
> >>
> >>pg_upgradecluster -v 9.5 9.4 main
> >>
> >>was using that?
> >
> >True enough. I did specify the "-m u
On Fri, Jan 08, 2016 at 07:41:09AM -0800, Adrian Klaver wrote:
> >>I thought --method=dump was the default, so this:
> >>
> >>pg_upgradecluster -v 9.5 9.4 main
> >>
> >>was using that?
> >
> >True enough. I did specify the "-m upgrade" though, as
> >witnessed by the log snippet.
>
> Alright then.
On Fri, Jan 08, 2016 at 10:45:27AM -0500, Tom Lane wrote:
> Karsten Hilbert writes:
> > (For what it's worth, I have also tried the --method=dump way
> > of using Debian's pg_upgradecluster which internally uses a
> > dump/restore cycle rather than calling pg_
On Fri, Jan 08, 2016 at 10:45:27AM -0500, Tom Lane wrote:
> Karsten Hilbert writes:
> > [ pg_upgrade failed on pg_trgm ]
>
> Just for completeness, can you tell us which pg_trgm version (1.0
> or 1.1) is installed in the 9.4 database?
Sure:
(pg_trgm,1.1,"text
On Fri, Jan 08, 2016 at 11:12:09AM -0500, Tom Lane wrote:
> > Sure:
> > (pg_trgm,1.1,"text similarity measurement and index searching based on
> > trigrams")
>
> Hm. I just tried running a pg_upgrade here on a 9.4 database containing
> pg_trgm 1.1, and didn't see any particular problem, so
Again, as the list software doesn't like "config" at the
start of a line.
Karsten
On Fri, Jan 08, 2016 at 05:34:00PM +0100, Karsten Hilbert wrote:
> > > (For what it's worth, I have also tried the --method=dump way
> > > of using Debian's pg_upgrad
On Fri, Jan 08, 2016 at 10:45:27AM -0500, Tom Lane wrote:
> > (For what it's worth, I have also tried the --method=dump way
> > of using Debian's pg_upgradecluster which internally uses a
> > dump/restore cycle rather than calling pg_upgrade. That
> > failed due to ordering problems with table da
On Fri, Jan 08, 2016 at 12:53:24PM -0500, Tom Lane wrote:
> >> and here is the function that leads to the schema having a
> >> dependancy on table data:
>
> Hm. So, by having installed this function as a check constraint, you have
> created a data dependency that pg_dump has no way to know about
On Fri, Jan 08, 2016 at 12:38:47PM -0500, Tom Lane wrote:
>>> dumps of your 9.4 installation's databases. If you'd be willing to send
>>> those to me off-list, maybe I could figure out what's happening.
>
>> The list stalled the attachment so here as PM.
>
> Well, you shouldn't have tried to se
On Fri, Jan 08, 2016 at 12:38:47PM -0500, Tom Lane wrote:
> After digging through this, I figured out the problem: you'd installed
> pg_trgm into the pg_catalog schema, whereas when I was testing I'd just
> dropped it into the public schema. That confuses pg_dump into not
> emitting the shell typ
On Fri, Jan 08, 2016 at 04:03:51PM -0500, Tom Lane wrote:
> BTW, the one-liner fix that I'd had in mind when I wrote that does indeed
> fix this particular problem, but after studying the code I realized that
> there's a whole bunch of related problems; for instance I believe
> pg_upgrade would lo
On Fri, Jan 08, 2016 at 12:53:24PM -0500, Tom Lane wrote:
> In general, embedding lookups of other tables into CHECK constraints
> is going to cause you all kinds of grief quite aside from pg_dump
> not understanding it, because the backend doesn't really understand it
> either. If the other tabl
On Fri, Jan 08, 2016 at 04:26:25PM -0500, Tom Lane wrote:
> Karsten Hilbert writes:
> > On Fri, Jan 08, 2016 at 04:03:51PM -0500, Tom Lane wrote:
> >> BTW, the one-liner fix that I'd had in mind when I wrote that does indeed
> >> fix this particular proble
On Fri, Jan 08, 2016 at 12:53:24PM -0500, Tom Lane wrote:
> Hm. So, by having installed this function as a check constraint, you have
> created a data dependency that pg_dump has no way to know about. It's
> going to load the tables in some order that's chosen without regard to the
> need for de
nd
sublevels of politeness for each and every situation.
Karsten Hilbert
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Mon, Jan 11, 2016 at 09:13:32AM +0300, Oleg Bartunov wrote:
> Some people don't understand all these issues with she/he, for example, we
> in Russia are not really concern about this.
Russian offers a "Mr.Bartunov" and a "Mrs.Bartunova". Am I mistaken ?
concern about this.
> >
> > Russian offers a "Mr.Bartunov" and a "Mrs.Bartunova". Am I mistaken ?
> >
> > Karsten Hilbert
>
> Yes, but I guess Oleg meant pronouns in documents.
> In situations like 'When the user has to do something, firstly _
On Mon, Jan 11, 2016 at 12:57:11PM +0300, Yury Zhuravlev wrote:
> >OTOH, there's a whole bunch of words denoting levels and
> >sublevels of politeness for each and every situation.
> Politeness but not gender differences. Perhaps just for kids (-chan/-kun).
Well, traditionally not. But kare/kano-
tion on this one ?
It seems a bit narrow ?
Thanks,
Karsten Hilbert
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.po
..
Since I am using PostgreSQL for storing Electronic Medical
Record data I fear I will need to be able to discuss schema
layout related to gender, sexual orientation, disability,
physical appearance, body size, and race.
Karsten Hilbert
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167
reat idea in that
it is all-encompassing and using a generic concept to nicely solve a
specific (class of) problem(s) and then some.". Entirely reasonable (if
a bit unusually worded) in German :-)
Karsten Hilbert
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Please consider the following:
- Debian
- server is PG 9.4.5
- client (psql/pg_dump/libpq5) is 9.5
create table parent (
not_null_in_parent integer not null
);
create table child() inherits (parent);
alter table child
alter column n
On Wed, Jan 13, 2016 at 12:10:15PM -0800, Adrian Klaver wrote:
> On 01/13/2016 11:38 AM, Karsten Hilbert wrote:
> > create table parent (
> > not_null_in_parent integer not null
> > );
> >
> > create table child() inherits (p
On Wed, Jan 13, 2016 at 03:32:12PM -0500, Tom Lane wrote:
> Karsten Hilbert writes:
> > create table parent (
> > not_null_in_parent integer not null
> > );
>
> > create table child() inherits (parent);
> > alter tabl
age seems OK with me -- has there been
consensus as to whether we actually want/need a CoC ?
Thanks,
Karsten Hilbert
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To mak
On Wed, Jan 20, 2016 at 01:05:15PM -0600, Kevin Grittner wrote:
>>> * When interpreting the words and actions of others, participants
>>> should always assume good intentions.
...
> That came about because of the point made by someone for whom
> English is a second language, who attempted to compl
On Fri, Jan 22, 2016 at 02:51:24PM -, FarjadFarid(ChkNet) wrote:
> The number of job losses around the world is huge. From mining to retail or
> software industry.
> The writings is on the wall for large co-operates, especially where software
> is concerned.
>
> All the predictions are po
stening to everyone's needs.
> Identifying next major requirements and implementing it before the
> competition.
Indeed. And PostgreSQL's been brilliant with that so
far even without a CoC.
A wholehearted Thank You! to all having worked/working on PostgreSQL !
Karsten Hilbert
on beh
On Fri, Jan 22, 2016 at 04:47:43PM -0300, Luz Violeta wrote:
> P.S → even now, I'm kinda terrified of a shitstorm in my first mail to the
> mailing list ... but definitely this spark of hope made me come forward and
> say something, dunno.
Not that I've got much to say around here ;-) but, welco
On Fri, Jan 22, 2016 at 07:05:49PM +, Geoff Winkless wrote:
> Postgres developers believe that it's not their job to implement
> social justice, and instead decided to implement what they believe to
> be an acceptable compromise.
In fact, they decided to implement PostgreSQL - and I cannot
th
On Fri, Jan 22, 2016 at 04:47:43PM -0300, Luz Violeta wrote:
> It's sad, because all those who participated in the discussion were people
> that are not exposed to the experiences we live (and by that, I mean
> everyone not fitting in the hegemony of that white guy in the IT industry),
> and by co
1 - 100 of 642 matches
Mail list logo
