On 5 June 2018 at 17:34, Ozz Nixon wrote:
> Sorry...
>
> > 1) CoC might result in developers leaving projects
>
>
> I know this on going regurgitation is going to cause my team to
> leave the project, right around 100 posts on this off topic topic it
> was bad enough when the original
On Sun, 20 Oct 2019 at 08:32, Andrew Dunstan
wrote:
>
> Understood. I think the real question here is what it should do instead
> when the value is NULL. Your behaviour above is one suggestion, which I
> personally find intuitive. Another has been to remove the associated
> key. Another is to ret
I use a script to restore a backup to create a testing copy of the
database. I set the following in postgresql.auto.conf:
recovery_target = 'immediate'
recovery_target_action = 'promote'
In the logs I get "recovery stopping after reaching consistency" then a
moment later "database system is ready
On Fri, 3 May 2024 at 17:28, Tom Lane wrote:
This is one of the places where it's unfortunate that our English-text
> rule for quoting a string to set it off from the rest of the error
> message collides with SQL's rule for quoting an identifier. Leaving
> out the outer quotes would be contrary
On Wed, 22 May 2024 at 10:15, Greg Sabino Mullane
wrote:
> This is a good candidate for a window function. Also note that nulls
> already get sorted correctly by the DESC so no need to get 'infinity'
> involved, although you could write 'DESC NULLS FIRST' to be explicit about
> it.
>
> with x as
On Wed, 22 May 2024 at 11:36, Greg Sabino Mullane
wrote:
> Oh, you are right - NULLS LAST, got my -infinity crossed with my infinity.
> :)
>
NULLS LAST for lower bound, NULLS FIRST for upper bound.
The other way around if you were doing an ascending sort.
On Wed, 22 May 2024 at 13:48, Ron Johnson wrote:
As a superuser administrator, I need to be able to see ALL tables in ALL
> schemas when running "\dt", not just the ones in "$user" and public. And I
> need it to act consistently across all the systems.
>
\dt *.*
But I am skeptical how often yo
On Tue, 11 Jun 2024 at 18:25, Ron Johnson wrote:
Since all the functions are going to be similar, I'd write a shell script
> to generate all the triggers, one per relevant. If you're going to record
> every field, then save effort, and don't bother enumerating them. You'll
> need to dig into th
On Wed, 26 Jun 2024 at 08:42, David G. Johnston
wrote:
> On Wednesday, June 26, 2024, Dominique Devienne
> wrote:
>
>> Only session_user
>> is representative of the caller, and reliable (modulo SUPERUSER and
>> SET AUTHORIZATION, but that's a different story and kinda normal)
>>
>
> Why can you
On Fri, 3 Jan 2025 at 18:22, Jan Behrens wrote:
> Instead, I plan to expect the function to receive a query string that
> will get the data that is being processed by the function.
>
> That query string should be allowed to refer to tables in the
> search_path at the caller's side.
>
> Therefore
On Sun, 15 Dec 2024 at 12:29, Tom Lane wrote:
> What I'd suggest as an improvement that could be implemented
> immediately is to wrap the checks in a user-defined function
> like "is_system_schema(nspname name)".
>
Would it make sense to make the parameter be of type regnamespace?
On Sun, 15 Dec 2024 at 14:20, Tom Lane wrote:
> Isaac Morland writes:
> > On Sun, 15 Dec 2024 at 12:29, Tom Lane wrote:
> >> What I'd suggest as an improvement that could be implemented
> >> immediately is to wrap the checks in a user-defined function
> >
On Sun, 12 Jan 2025 at 17:59, Tom Lane wrote:
> "Peter J. Holzer" writes:
> > The web framework Django will automatically and transparently rehash any
> > password with the currently preferred algorithm if it isn't stored that
> > way already.
>
> Really? That implies that the framework has acc
13 matches
Mail list logo
